I should detail that the back end web service is an AXIS application (I don't know too much about it). Traffic that doesn't require a web service call using username and password works. It's only the web service communication using username and password where it fails. On Wed, Jun 18, 2008 at 8:20 PM, Gary Tai <gary.c.tai@xxxxxxxxx> wrote: > Yes, sorry I didn't state, but it is a Reverse Proxy. > > So, the "login=PASS" parameter will forward the encoded username and > password to the backend application? > > I'll give it a try. > > Thanks. > > > On Wed, Jun 18, 2008 at 6:30 PM, Henrik Nordstrom > <henrik@xxxxxxxxxxxxxxxxxxx> wrote: >> On ons, 2008-06-18 at 17:08 -0400, Gary Tai wrote: >> >>> >From the application documentation: >>> Web services requires a client to provide credentials as BASIC HTTP >>> user authentication. BASIC authentication encrypts the user ID and >>> password with Base64 encoding and passes it as an HTTP request header >>> parameter. >> >> Is this a reverse proxy? If so see the last question here: >> http://wiki.squid-cache.org/SquidFaq/ReverseProxy#head-c59962b21bb8e2a437beb149bcce3190ee1c03fd >> >> Regards >> Henrik >> >