When I try to bind to my service locator url at https://<uid>:<pwd>@<host>:<port>/path/to/service with a pwd that has '/' in it, I fail to bind to the backend. I encode the url prior to attempting to bind to the service. I can see that encoding of '/' into %2F works properly. The binding is successful with other uid/pwd that do not include '/'. If I try to go to https://<uid>:<pwd>@<host>:<port>/path/to/service in my browser with '/' replaced with '%2F' that also works fine and I get in successfully. Can you shed some light into what might be happening ? I was suspecting may be an issue with service locator url encoding and axis ? Lerna Ekmekcioglu --------------------------------------------------------
NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
