Skip to Content
author's profile photo Former Member
Former Member

Proxy Authentication Required in a Web Service call

Hi, we have a problem with our WebService.

In fact we created a webservice using the eclipse plugins.

We now have a webservice project with a portalapp.xml file which is the following :

<?xml version="1.0" encoding="iso-8859-1"?>

<application alias="WebServicePlanchettes">


<property name="SharingReference" value="">






<service name="WebServicePlanchettes" alias="WebServicePlanchettes">


<property name="className" value="com.stibmivb.portal.service.WebServicePlanchettes.WebServicePlanchettes">


<property name="startup" value="true">


<property name="WebEnable" value="true">


<property name="WebProxy" value="false">


<property name="SecurityZone" value="">






The problem is that we always receive an error telling :

javax.xml.soap.SOAPException: Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy service is denied. ) (proxy host:, proxy port: 80, non proxy host: localhost||portdev.|sto1513s)

But the URL of our WebService is http://sto1513s/planchettesXML/planchettesXML.asmx and this server is listed in the non-proxy hosts !

We've added it using the J2EE config tool and also via the portal itself by editing the proxy object of the service.

After these changes we've restarted the Server.

Has anybody an idea why our webservice seems to still try to go through the proxy ?

Thank you in advance,


Add comment
10|10000 characters needed characters exceeded

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jun 18, 2004 at 08:20 AM

    Still no answer ... Nobody uses WebServices here ?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      We found the problem.

      In fact in the documentation they said to use the "|" character to separate the server that don't have to pass via a proxy, but in fact you should use "," !

      If somebody else encounters this, just replace the "|" by "," in the http service and restart the service.