On 24/03/2016 4:33 a.m., Waitman Gobble wrote:
>
> I made a little test program and now I see what's going on, maybe this
> isn't actually a squid problem.. It's returning
> 'HTTP/1.1 200 Connection established'
> through proxy SSL , then a space, then the actual headers. The other day
> I did not
On 2016-03-19 04:50, Waitman Gobble wrote:
On 2016-03-18 01:00, Amos Jeffries wrote:
On 18/03/2016 3:46 a.m., Waitman Gobble wrote:
When a script reference on an HTML page includes a parameter, the
script
does not appear to be cached when using squid in accel mode (https).
For example,
j
On 20/03/2016 12:50 a.m., Waitman Gobble wrote:
>
>
> On 2016-03-18 01:00, Amos Jeffries wrote:
>
>> On 18/03/2016 3:46 a.m., Waitman Gobble wrote:
>>
>>> When a script reference on an HTML page includes a parameter, the script
>>> does not appear to be cached when using squid in accel mode (htt
On 2016-03-18 01:00, Amos Jeffries wrote:
On 18/03/2016 3:46 a.m., Waitman Gobble wrote:
When a script reference on an HTML page includes a parameter, the
script
does not appear to be cached when using squid in accel mode (https).
For example,
jquery.js does not appear to be cached in th
When a script reference on an HTML page includes a parameter, the script
does not appear to be cached when using squid in accel mode (https).
For example,
src='/wp-includes/js/jquery/jquery.js?ver=1.1.13'>
jquery.js does not appear to be cached in that case, each page request
hits the o
On 18/03/2016 3:46 a.m., Waitman Gobble wrote:
>
> When a script reference on an HTML page includes a parameter, the script
> does not appear to be cached when using squid in accel mode (https).
>
> For example,
> src='/wp-includes/js/jquery/jquery.js?ver=1.1.13'>
>
> jquery.js does not appear
