On 8/06/2016 8:21 a.m., Heiler Bemerguy wrote:
>
> Some servers will reply like this, trying to avoid caching at any cost
> (I think):
>
> HTTP/1.1 200 OK
> Server: nginx
> Content-Type: image/x-icon
> Last-Modified: Tue, 07 Jun 2016 11:16:55 GMT
> ETag: "5756ad27-47e"
> Content-Length: 1150
> X-
On 8/06/2016 10:27 a.m., Heiler Bemerguy wrote:
>
> I changed the source to debug a bit, started a fresh/clean squid.
>
> accessed http://api.footballaddicts.com/favicon.ico
>
> and look what it's trying to compare():
>
> vary =
> 'accept="text%2Fhtml,application%2Fxhtml+xml,application%2Fxml%3
On 8/06/2016 5:08 a.m., Adam Vollrath wrote:
> Good morning! I'm having trouble with upstream HTTP servers not
> responding for more than 30 seconds. I'd like to just return an empty
> response to the downstream client. Nothing is better than waiting.
>
> I'm looking for a `squid3` configuration
I changed the source to debug a bit, started a fresh/clean squid.
accessed http://api.footballaddicts.com/favicon.ico
and look what it's trying to compare():
vary =
'accept="text%2Fhtml,application%2Fxhtml+xml,application%2Fxml%3Bq%3D0.9,*%2F*%3Bq%3D0.8",
if-none-match="%225756ad27-47e%22",
Some servers will reply like this, trying to avoid caching at any cost
(I think):
HTTP/1.1 200 OK
Server: nginx
Content-Type: image/x-icon
Last-Modified: Tue, 07 Jun 2016 11:16:55 GMT
ETag: "5756ad27-47e"
Content-Length: 1150
X-Suppressed-Cache-Control: max-age=600
Cache-Control: private, max-
On 8/06/2016 2:12 a.m., Paul Buechler wrote:
I've tested every %st-tag and read the whole documentation.
What i want to see is, that if i upload 100Mb -> the log says 1
On 08.06.16 05:36, Amos Jeffries wrote:
100 Mb == 13,107,200 Bytes.
100 MB == 104,857,600 Bytes.
Actually is Mib
On 8/06/2016 2:12 a.m., Paul Buechler wrote:
> I've tested every %st-tag and read the whole documentation.
>
> What i want to see is, that if i upload 100Mb -> the log says 1
100 Mb == 13,107,200 Bytes.
100 MB == 104,857,600 Bytes.
100,000,000 Bytes == 95.4 MB
100,000,000 bits == 11.9
Good morning! I'm having trouble with upstream HTTP servers not
responding for more than 30 seconds. I'd like to just return an empty
response to the downstream client. Nothing is better than waiting.
I'm looking for a `squid3` configuration directive to timeout between an
HTTP request and respon
I've tested every %st-tag and read the whole documentation.
What i want to see is, that if i upload 100Mb -> the log says 1
caused by a tag. None of the %st-tags showed me this value. Neither
%st.
So is there going to be a tag in the near future to show the complete
size of an upload
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I want to give one example on the topic.
Here is from one of my cache:
/data/cache/d2/00/02/04C3 0 102502
http://www.openoffice.org/favicon.ico
/data/cache/d2/00/01/031D 0 161421
http://rgho.st.squidinternal/favicon.ico
/data/cach
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The world is not perfect, unfortunately. The ivory tower is revered
standards and regulations. In the real world they spit when it is
profitable. Especially when this recommendation and not rigid protocol
requirements. :)
We are also talking about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
You see, Vary the standard, however, if you had to see how the site is
added to the garbage sequence response headers to prevent its cache? I
had very often.
What kind of standards we say, when the same scale Google deploys custom
protocol complet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
07.06.2016 17:00, Amos Jeffries пишет:
> On 7/06/2016 9:12 p.m., Yuri Voinov wrote:
>>
>>
>>
>> 07.06.2016 5:13, Amos Jeffries пишет:
>>> On 7/06/2016 6:20 a.m., Yuri Voinov wrote:
By the way, we have another problem. Caching is greatly
On 7/06/2016 9:12 p.m., Yuri Voinov wrote:
>
>
>
> 07.06.2016 5:13, Amos Jeffries пишет:
>> On 7/06/2016 6:20 a.m., Yuri Voinov wrote:
>>>
>>> By the way, we have another problem. Caching is greatly reduced by the
>>> presence of User-Agent header Vary. Although I know that Amos says - he
>>> sa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
07.06.2016 16:36, Amos Jeffries пишет:
> On 7/06/2016 8:48 p.m., Yuri Voinov wrote:
>>
>> 07.06.2016 4:57, Amos Jeffries пишет:
>>> On 7/06/2016 5:55 a.m., Yuri Voinov wrote:
So.
Squid DOES NOT and DON'T BE support gzip. The o
On 7/06/2016 8:48 p.m., Yuri Voinov wrote:
>
> 07.06.2016 4:57, Amos Jeffries пишет:
>> On 7/06/2016 5:55 a.m., Yuri Voinov wrote:
>>>
>>> So.
>>>
>>> Squid DOES NOT and DON'T BE support gzip. The only way to do it - use
>>> ecap + desupported ecap gzip adapter. Let's accept this. We can support
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
BTW, Amos.
As Gzip adapter in great demand due to the Squid,and it not maintained
right now, maybe Alex will conjunct it to the other ecap adapters
within Measurement Factory? Somehow, as loadable part of eCap.
Compression is very popular on the
On 7/06/2016 10:39 a.m., Yuri Voinov wrote:
>
>
>
> 07.06.2016 4:26, Amos Jeffries пишет:
>> On 6/06/2016 8:10 p.m., Yuri wrote:
>>> Heh,
>>>
>>> and breaking Internet...
>
>> No it does not. Every HTTP agent has mandatory support for un-encoded
>> objects. The use of encodings is optional.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
07.06.2016 5:13, Amos Jeffries пишет:
> On 7/06/2016 6:20 a.m., Yuri Voinov wrote:
>>
>> By the way, we have another problem. Caching is greatly reduced by the
>> presence of User-Agent header Vary. Although I know that Amos says - he
>> says, we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
07.06.2016 4:57, Amos Jeffries пишет:
> On 7/06/2016 5:55 a.m., Yuri Voinov wrote:
>>
>> So.
>>
>> Squid DOES NOT and DON'T BE support gzip. The only way to do it - use
>> ecap + desupported ecap gzip adapter. Let's accept this. We can support
>>
20 matches
Mail list logo
