Dear all,

Yesterday I found out this problem:

I wrote a servlet setting and retrieving cookies. To make sure the value of the 
cookies does not contain strange characters, I en/decode this value as Base64.
I tested the servlet on a development machine (W2K - tomcate 4.0.1 standalone) and 
every thing went well.
Next I deployed the webapp containing my servlet on a production server (W2K server 
prof. - tomcat 4.0.1 - isapi redirector) and appearently the values of the retrieved 
cookies came back as sent but url-encoded.
As you all now, this shouldn't cause a problem (because it was base64 endoded) except 
for that last '=' character base64 strings often end with.
When I accessed the webapp through port 8080 (not through IIS) the values of the 
cookies entered normal again.

Looks to me as a bug in the redirector.

Greetings, Maarten

Reply via email to