Alex, thank you for the quick reply. They are not actually passing a url to the squid server. The nginx config allowed me to have a line as such: proxy_pass https://calcconnect.vertexsmb.com/vertex-ws/services/CalculateTax The xml just got passed straight through to the url in the config file. Is there something comparable in squid I can set to tell it where to pass the code? I am working on getting the wireshark packets but the server is in a secure zone so there aren't any easy options for getting a file from it. Thanks~ Cindy -----Original Message----- From: Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx> Sent: Friday, May 1, 2020 11:26 AM To: Cindy Yoho <Cyoho@xxxxxxxxxxxxxxxx>; squid-users@xxxxxxxxxxxxxxxxxxxxx Subject: [External] Re: Passing XML through squid proxy On 5/1/20 10:56 AM, Cindy Yoho wrote: > When the Order Entry server sends the XML code, we get an error > returned to the server making the request Perhaps your Order Entry server does not use HTTP when talking to Squid? Squid does not really care about the request payload, but the request has to use the HTTP transport protocol. So sending a SOAP/XML request payload over HTTP is OK, but sending raw SOAP (or SOAP over something other than HTTP) is not. If you can post a packet capture of the Order Entry server talking to Squid (not the text interpretation of Squid response but the actual packets going from the Order Entry server to Squid; use libpcap format which is often the default for Wireshark export), then we should be able to confirm whether your Order Entry server is using the right protocol to talk to/through Squid. The same packet capture can point to HTTP request problems if the Order Entry server is using HTTP but sending some HTTP token that Squid does not like (or not sending an HTTP token that Squid needs). HTH, Alex. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
