Squid v3.3 asserts after newRequest()
Hi,
I developed an adapter which is an interface between squid and external software (library). This library outputs plain text headers to inject, so instead of using clone(), I inject these headers using newRequest() or newResponse() methods and then parse() plain text header into header object. The problem here is that newResponse() works well, while newRequest() makes squid bail out with messages:
2015/12/13 01:16:40.460| client_
---------
GET http://
User-Agent: Wget/1.15 (linux-gnu)
Accept: */*
Host: www.hidden.com
Connection: Close
Proxy-Connection: Keep-Alive
----------
2015/12/13 01:16:40.464| client_
2015/12/13 01:16:40.464| assertion failed: client_
The example adapter code (simplified for the sake of demonstration):
void Adapter:
const libecap::Header *h;
h = &(hostx-
}
As I said, pretty much the same piece of code is ok, when used after newResponse()... Should I do something specific to make the above work? My first guess is that this is squid's bug, so I'm currently compiling newer version (3.4.14, I don't want to mess to much with dependencies, including libecap in squid 3.5).
The host I'm testing this on is: Ubuntu 14.04 LTS x86_64, libecap 0.2.0, squid 3.3.8.
Best Regards
BL
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- eCAP Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Bartłomiej Leszak
- Solved:
- Last query:
- Last reply: