Hi Conal
" Check the Alerts tab under the monitoring section in ISA Server
Management console. You should see the exact reason for the header being
rejected." [1] - does this help?
Also, what exactly is the full response you get as seen through
wireshark? Could you post a new example? Also, you could check if the
correct credentials went through by checking the decoded basic auth
string. Try something that works too (any request through the proxy) and
post it, so that its easier to figure out which header is the problem ..
I suspect transfer encoding..
cheers
asankha
[1]
http://www.experts-exchange.com/Other/Miscellaneous/Q_21903188.html?sfQueryTermInfo=1+connecto
Below are the headers captured using wireshark.
POST http://xxxxxx.xxxxxxxx.com/xxxxxdatawebservice/xxxxquery.asmx
HTTP/1.1\r\n
Request Method: POST
Request URI:
http://xxxxxxx.xxxxxxxxx.com/xxxxxxdatawebservice/xxxxxxquery.asmx
Request Version: HTTP/1.1
Content-Type: application/soap+xml; charset=UTF-8;
action="http://xxxx.xxxxxxxx.com/xxxxxDataWebService/xxxxxQuery/Queryxxx
xxx"\r\n
User-Agent: Axis2\r\n
Proxy-Authorization: Basic bWFxxxxxxxx==\r\n
Credentials: xxxxxxx:xxxxxxxxx
Host: idstaging.moneymate.com\r\n
Proxy-Connection: Keep-Alive\r\n
Transfer-Encoding: chunked\r\n
\r\n
--
Asankha C. Perera
http://adroitlogic.org
http://esbmagic.blogspot.com
