Ali Jawad wrote:
Without SQUID
The packet is
POST /balance2.php HTTP/1.1.
Host: xyz
content-type: application/x-www-form-urlencoded.
Connection: Keep-Alive.
content-length: 36.
.
username=sourceedge2&password=123456
I assume you are consistent with using '.' as a newline.
The Host: header is a bit broken. If thats not a typo it will cause
Squid to reject the POST.
With SQUID the request is:
POST /balance2.php HTTP/1.0.
Host: xyz.com.
Content-Type: application/x-www-form-urlencoded.
Content-Length: 36.
Via: 1.1 y.net:3128 (squid/2.6.STABLE5).
X-Forwarded-For: 127.0.0.1.
Cache-Control: max-age=259200.
Connection: keep-alive.
As you can see the argument line is missing and the server returns with:
HTTP/1.1 200 OK.
Date: Mon, 25 Jan 2010 18:19:38 GMT.
Server: Apache/2.2.3 (CentOS).
X-Powered-By: PHP/5.1.6.
Content-Length: 35.
Connection: close.
Content-Type: text/html; charset=UTF-8.
.
Error passing variables (AD err 01)
On Mon, Jan 25, 2010 at 6:30 PM, Ali Jawad <alijawad1@xxxxxxxxx> wrote:
Hi
We are developing an application that does send XML requests to our
webserver. We do have a non caching SQUID server on our local network,
when the SQUID server is in use we dont get the result back from the
server. When we dont use the SQUID server we get the result. Although
no content filtering rules are are in place. If the request is done
through a browser we get the answer
This is the SQUID log for a browser
1264444735.732 1748 127.0.0.1 TCP_MISS/200 623 GET
http://xyz.com/balance2.php? - DIRECT/87.236.144.25 text/xml
This is the SQUID log for our application
1264444752.166 60004 127.0.0.1 TCP_MISS/000 0 POST
http://xyz.com/balance2.php - DIRECT/87.236.144.25 -
As for the server itself
This is the log when passing through SQUID with application
sourceIP - - [25/Jan/2010:17:17:44 +0000] "POST /balance2.php HTTP/1.0" 200 35
This is the log when NOT passing through SQUID with application
sourceIP - - [25/Jan/2010:17:18:55 +0000] "POST /balance2.php HTTP/1.1" 200 82
Can anyone please point me in the right direction ?
Regards
TCP_MISS/000 means something broke before Squid received any reply
information to pull the status code from.
I'd raise the debug level to "debug_options 11,5 55,5 58,5 73,6 74,6"
and see what information is available about the problem.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE7 or 3.0.STABLE21
Current Beta Squid 3.1.0.15
