Search squid archive

Re: Priority of http over https traffic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



squid squid wrote:
 <4AF3FEC8.3000100@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


Hi,
Thank you for the reply. WOuld like to know if the treating of all requests are equal is the same across all version of squid??? Regards.


In general yes.
In practice, each version has differing levels of resource usage by certain requests GET vs POST, memory-sourced vs disk-sourced, vs network sourced.

PURGE has not altered significantly since 2.5 AFAIK.
* The cache_dir handling does differ between storage types (ufs, aufs, diskd, coss) rather than Squid version. * Some releases of Squid-2.7 have differences in what PURGE does dues to Vary: header handling.

Amos

----------------------------------------
Date: Fri, 6 Nov 2009 23:47:36 +1300
From: squid3@xxxxxxxxxxxxx
CC: squid-users@xxxxxxxxxxxxxxx
Subject: Re:  Priority of http over https traffic

squid squid wrote:
Hi,



Currently I am running Squid Version 2.7 Stable 4 on a Linux ES3 box
with 2.5GB RAM.



Basically there is no caching configured on the squid apps and it is
being used like a middle man between client and web/apps servers
which has both http and https transaction



Would like to know does squid application give higher priority for
http transaction as compared to https transaction??? That is to say,
a client who access http traffic will get serve by squid apps first
and client who access https traffic will get server later.

No it does not. All requests are equal.

This can be manually changed by using delay_pools to limit available
bandwidth to certain requests.


Kindly also advise is there any way to have detailed logging for
https connection passing thru squid cause the current log only
capture "CONNECT xxx.xxx.com:443" which does not show the actual
status of the transaction.
Not in Squid-2. What you see logged _is_ the entire connection data
available to Squid-2.

Squid-3.1 can go deeper with SslBump, but requires administrative
control over the encryption certificates on the client machine to do so.

Amos
--
Please be using
Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20
Current Beta Squid 3.1.0.14
_________________________________________________________________
New Windows 7: Find the right PC for you. Learn more.
http://windows.microsoft.com/shop


--
Please be using
  Current Stable Squid 2.7.STABLE7 or 3.0.STABLE20
  Current Beta Squid 3.1.0.14

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux