[squid-users] Squid 5.2 TCP_MISS_ABORTED/100 erros when uploading

[Alex Rousskov]

On 8/29/22 06:17, David Ferreira wrote:

> I have some squid's running on rocky linux 8 with verion 4.15, recently 
> been testing squid version 5.2(stable version that comes with Rocky 9)to 
> upgrade the current ones and most of the configs/acls seem to work fine.
> 
> Unfortualy theres an application that we use that everytime it tries to 
> upload files it fails on squid 5.2, on 4.15 is works completly fine, so 
> far ive test on squid 5.2 and 5.5 and it's the same behavior, im testing 
> this with default configurations and it always works on 4.15, access log 
> only shows this:
> 
> Squid 4.15:
> 26/Aug/2022:15:36:08 +0100    273 172.19.222.132TCP_MISS/200 745 POST http://websiteurl/index.php - HIER_DIRECT/websitedomain text/xml
> 
> Squid 5.2:
> 25/Aug/2022:15:10:00 +0100    139 172.19.222.132 TCP_MISS_ABORTED/100 0 POST http://websiteurl HIER_DIRECT/websitedomain -
> 
> anyone has an ideia of what may be happening here?, been searching about 
> http errors 100 and so far i did not find anything that points me to the 
> problem.
> 
> On the application side the error it shows when it tries to upload is:
> "
> Error storing the document on the server
> Detail HTTP error 100
> Send failure: Connection was aborted (55)
> "

Squid v5.2 has many serious bugs. I would not use it in production. 
Build the latest Squid v5 from sources if you have to.


If the latest Squid v5 shows the same problem then this is probably a 
client application or Squid bug/misconfiguration. There were quite a few 
changes in HTTP 1xx control message handling since Squid v4, and one of 
those changes is probably affecting your client. For example, either 
Squid v4 does not deliver that 100 control message to the client at all 
or it is delivering a slightly different 100 control message that your 
client is happy with.
  If you share what HTTP messages are exchanged between client and Squid 
and between Squid and the origin server, in both successful and failing 
use cases, we may be able to tell you more. I would use tcpdump, 
wireshark, or a similar tool to collect HTTP traffic since these are 
non-TLS transactions.


HTH,

Alex.