I don't believe these clients entered non-ASCII chars as they are from North
America.
Regards,

SZ


On Mon, Mar 16, 2009 at 6:53 PM, Arno Garrels <arno.garr...@gmx.de> wrote:

>  Fastream Technologies wrote:
> > Hello,
> >
> > They cannot say what's wrong at all--not even a clue, just "doesn't
> > work!". My implementation is in the SSL tabsheet of the GUI of:
> >
> > http://www.fastream.com/beta/IQReverseProxy.exe
> >
> > Customers complain. :(
> >
> > Any idea?
>
> No idea, the CSRs created have been tested with OpenSSL.exe and XCA
> (a free GUI OpenSSL CA, available at sourceforge.net).
> Unless the reason is known why those requests are refused by Verisign
> I have no idea.
>
> Most commercial CAs provide some webservice to create certificate
> requests online, I would use them rather than a self generated request.
>
> Maybe they require certain fields or maybe your customers enter non-ASCII
> chars. AFAIR ICS v7 now uses UTF-8 encoded requests if any char is beyond
> #127.
>
> --
> Arno Garrels
>
>
>
> --
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be
>
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to