On 2024-04-24 21:23, Arun Kumar wrote:
I managed to reproduce the problem in my personal setup. Please find the
cache logs when the problem is reproduced. Squid version is 5.8
Just to close this old thread: My response[1] on a newer thread
(analyzing the same log file you shared on this thread
I managed to reproduce the problem in my personal setup. Please find the cache
logs when the problem is reproduced. Squid version is 5.8
https://drive.google.com/file/d/19yirXfxKli7NXon4ewiy-v3GpLvECT1i/view?usp=sharing
On Wednesday, April 24, 2024 at 09:16:23 PM EDT, Arun Kumar
wrote:
I managed to reproduce the problem in my personal setup. Please find the cache
logs when the problem is reproduced. Squid version is 5.8
cache.zip
| |
cache.zip
|
On Friday, March 22, 2024 at 11:02:51 PM EDT, Alex Rousskov
wrote:
On 2024-03-22 13:11, Arun Kumar wrote:
> The li
On 2024-03-22 13:11, Arun Kumar wrote:
The lines above are. The content-length is 138 (8a in hex), but the
bytes are 144. Could this be the reason?
parseMore: have 144 bytes to parse [FD 14;RBG/Comm(14)wr job24]
parseMore:
8a^M
{"activity":"Make a simple musical
instrument","type":"music","par
The lines above are. The content-length is 138 (8a in hex), but the bytes are
144. Could this be the reason?
parseMore: have 144 bytes to parse [FD 14;RBG/Comm(14)wr job24]parseMore:
8a^M{"activity":"Make a simple musical
instrument","type":"music","participants":1,"price:0.4,"link":"","key":"70
On 2024-03-18 18:46, Arun Kumar wrote:
Any idea, the reason for error in ModXact.cc parsePart fuction.
Happening during parsing the response from ICAP
parsePart: have 144 head bytes to parse; state: 0
parsePart: head parsing result: 0 detail: 600
AFAICT, Squid considers received ICAP response
Any idea, the reason for error in ModXact.cc parsePart fuction.Happening during
parsing the response from ICAP
parsePart: have 144 head bytes to parse; state: 0parsePart: head parsing
result: 0 detail: 600
___
squid-users mailing list
squid-users@list
