Problem translating servlet name from an encoded URL when using HTTPS

Question

Hello:
I am experiencing a wierd issue when using WLS 5.1 with HTTPS and am hoping someone might
be able to shed some light...
I have deployed a web application and am using HTTPS.
So, a typical call to a servlet is
https://foo.com/web_app_context/servlet_name/servlet_arguments
The servlet is used to upload files from disk to a database and to also download the same.
Therefore, the servlet_arguments string contains the file name among other things.
The problem seems to arise when the file name contains either a space or an
underscore e.g. "file_name" or "file name". It is then typically encoded as
"file%20name" in
the URL.
So a call then looks like:
https://foo.com/web_app_context/servlet_name/file%20name
When this request is sent to WLS, it seems to truncate the servlet_name by a couple
of characters causing the request to fail.
This works fine using HTTP.
Any thoughts would be much appreciated.
Thanks in advance.
Prashant

Answer 1

The JNDI call is different when you call an EJB from inside the J2EE.
ctx = new InitialContext();
ref = ctx.lookup("java:comp/env/<JNDI-Name>");
Regards
Stefan