Search squid archive

Re: squid no longer aborts bad request?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Kaiwang Chen wrote:
In 2.6.STALBE21,  squid immediately responds with 400 when I enter
'a'; while in 3.1.6 the connection expects more characters, although
it will definitively not get a good request.

[root@squid1 root]# telnet localhost 80
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
a
HTTP/1.0 400 Bad Request
Server: squid/2.6.STABLE21
...
Some aspect of the HTTP Request is invalid.  Possible problems:
Missing or unknown request method
Missing URL
Missing HTTP Identifier (HTTP/1.0)
Request is too large
(more...)
...


[root@dev ~]# telnet localhost 80
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
a

b
(can type in anything, and Ctrl-C will not abort connection. It just hang there)

Ctrl-C will not terminate telnet (Ctrl-] is needed for that) but yes I see the problem.



Is there a configuration directive that controls it?

No, just some sanity checks.


Looks like you have hit a bug in the HTTP/1.1 persistent connections when dealing with HTTP/0.9 ambiguous traffic.

I've reproduced that in the latest code and am working on it now, but could you please report it in bugzilla anyway so it doesn't get lost.

Amos
--
Please be using
  Current Stable Squid 2.7.STABLE9 or 3.1.7
  Beta testers wanted for 3.2.0.1


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux