Re: [squid-users] problems with some requests

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Wed, 29 Jan 2014 19:11:12 +1300

On 29/01/2014 6:55 p.m., m.shahverdi_at_ece.ut.ac.ir wrote:
> Hi,
> I have a problem with ftp and https requests.
> I'm running squid in debug mode to trace function calls for a ftp and a
> https request and finding below lines in cache.log:

What makes you think your Squid is capable of receiving HTTPS or FTP
request messages?

>
> for a https request I'm getting:
> **************
> client_side.cc(2862) clientParseRequests: local=216.239.32.20:443
> remote=10.1.116.50 FD 10 flags=17: attempting to parse
> HttpParser.cc(29) reset: Request buffer is 
> HttpParser.cc(39) parseRequestFirstLine: parsing possible request: 
> HttpParser.cc(248) HttpParserParseReqLine: Parser: retval -1: from 0->49:
> method 0->-1; url -1->-1; version -1->-1 (0/0)

First byte in HTTPs is binary. Which is invalid HTTP characters.

> **************
> In fact the request is unrecognizable for squid.
> and for a ftp request:
> **************
> AsyncCall.cc(30) make: make call ConnStateData::clientReadRequest [call39]
> AsyncJob.cc(117) callStart: ConnStateData status in: [ job3]
> client_side.cc(2923) clientReadRequest: local=10.1.116.49:22
> remote=10.1.116.50 FD 10 flags=17 size 0
> client_side.cc(2959) clientReadRequest: local=10.1.116.49:22
> remote=10.1.116.50 FD 10 flags=17 closed?
> client_side.cc(2401) connFinishedWithConn: local=10.1.116.49:22
> remote=10.1.116.50 FD 10 flags=17 closed
> comm.cc(1102) _comm_close: comm_close: start closing FD 10
> **************
> That's very wonderful! squid could not read request from socket!

* FTP protocol starts with the server announcing itself to the client.
* Your agent speaking FTP waits for that announcement.

* HTTP protocol starts with client announcing its request to the proxy
or server.
* Squid being an HTTP proxy waits for the request.

* After waiting a while for some traffic to happen TCP protocol simply
closes the socket.

Because:
1) Squid is "an HTTP caching proxy", not an FTP proxy **.

2) You have only configured Squid to receive explicit/direct proxy HTTP
traffic and TPROXY intercepted HTTP traffic.

> http_port 3128
> http_port 3129 tproxy

** FTP protocol relaying by Squid is being experimented with but not yet
available in any of the formal releases.

Amos
Received on Wed Jan 29 2014 - 06:11:18 MST

This archive was generated by hypermail 2.2.0 : Wed Jan 29 2014 - 12:00:06 MST