Ok, you have too little information.

network structure:

Client --> PW-Gateway intern (PWGi) --> PW-Gateway extern (PWGe) --> Proxy (throws the bad request) --> App-Server

If we use SSL, the CURLOPT_PROXY Option isn't set, because in this case a nameserver is used to route requests to the App-Server to the IP from the PWGi. The PWGi then forwards the request to the real App-Server adress.

The connection between the Client and the PWGi uses SSL. The PWGi is the SSL endpoint. The connection between the PWGi and the PWGe is encrypted with Private Wire. The next station ist the restrictive proxy, that throws the bad request.

I have tracked down that the POST URL is wrong.

> POST /servlets/tstOnline HTTP/1.1

This POST URL isn't RFC conform.

should be: POST https://tst-online.tst.de/servlets/tstOnline HTTP/1.1

If i don't use https, the POST URL is correct and looks like this:

POST http://tst-online.tst.de/servlets/tstOnline HTTP/1.1

If i test without SSL and change the header during the session and delete the protocol and the host from the POST URL, the proxy also reacts angry.

I hope, the problem comes now in a sharper relief.

best regards

Thomas Reinhardt

-- 
Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a
-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01