I want to know how the squid parse the body of certificate when they send HTTPS
requests and get the server's certificate.
The operation of this part is in which class or function.___
squid-users mailing list
squid-users@lists.squid-cache.org
http://list
On 11/01/2017 11:45 AM, Yuri wrote:
> 01.11.2017 23:37, Alex Rousskov пишет:
B) Use threads inside the adapter to make its operations asynchronous.
>>> AFAIK B) is impossible.
>> It is not only possible but implemented in sample and production
>> adapters (as I have said later in the same em
01.11.2017 23:37, Alex Rousskov пишет:
> On 11/01/2017 09:26 AM, Yuri wrote:
Is there a way other than
programming the eCAP adapter in asynchronous mode?
>>> I do not think there is a better alternative. AFAICT, you only have two
>>> options:
>>>
>>> A) Change Squid to move eCAP calls
On 11/01/2017 09:26 AM, Yuri wrote:
>>> Is there a way other than
>>> programming the eCAP adapter in asynchronous mode?
>> I do not think there is a better alternative. AFAICT, you only have two
>> options:
>>
>> A) Change Squid to move eCAP calls to thread(s).
>> B) Use threads inside the ad
01.11.2017 21:23, Alex Rousskov пишет:
> On 11/01/2017 03:20 AM, Christof Gerber wrote:
>
>> [Will Squid] be blocked until the eCAP API call returns?
> To answer the exact question above: Yes, the Squid worker making an eCAP
> API call will block until that call returns. The same is true for all
01.11.2017 21:23, Alex Rousskov пишет:
> On 11/01/2017 03:20 AM, Christof Gerber wrote:
>
>> [Will Squid] be blocked until the eCAP API call returns?
> To answer the exact question above: Yes, the Squid worker making an eCAP
> API call will block until that call returns. The same is true for all
01.11.2017 21:23, Alex Rousskov пишет:
> On 11/01/2017 03:20 AM, Christof Gerber wrote:
>
>> [Will Squid] be blocked until the eCAP API call returns?
> To answer the exact question above: Yes, the Squid worker making an eCAP
> API call will block until that call returns. The same is true for all
On 11/01/2017 03:20 AM, Christof Gerber wrote:
> [Will Squid] be blocked until the eCAP API call returns?
To answer the exact question above: Yes, the Squid worker making an eCAP
API call will block until that call returns. The same is true for all
other API calls, all system calls, and all inter
On 01/11/17 05:53, Alex Rousskov wrote:
On 10/31/2017 02:51 AM, Amos Jeffries wrote:
That operational state (HTTP underway) also means RFC 7230 is the
relevant place to look for behaviour requirements. Section 6.3.1 says:
A proxy MUST NOT automatically retry non-idempotent requests.
So
On 01/11/17 21:54, Vacheslav wrote:
Thanks for your time,
-Original Message-
From: Amos Jeffries
Sent: Tuesday, October 31, 2017 5:45 PM
On 31/10/17 22:05, Vacheslav wrote:
Peace,
I tired searching and debugging but I couldn’t find a solution,
whatever I do youtube keeps working.
Her
On 01/11/17 23:09, Torsten Luettgert wrote:
Hello,
we were wondering if it's possible to use HTTP headers in an external
store ID helper, not only the URL.
Depends on the header.
* Response headers do not exist when Store-ID helper is called.
* Request headers (and maybe ICAP REQMOD headers)
Hello,
we were wondering if it's possible to use HTTP headers in an external
store ID helper, not only the URL.
Any help/hints appreciated :-)
Thanks for your time,
Torsten
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squ
Hi everyone
I am working on an ecap adapter which attaches to Squid 3.5. The
adapter is going to make an external socket call which results in an
REST API call (lookup) which will cause a delay of some milliseconds
until the response is available. As ecap is blocking I assume Squid
will be blocke
13 matches
Mail list logo