On 06/02/2013 03:43 PM, Amos Jeffries wrote:
On 1/06/2013 5:14 a.m., Alex Rousskov wrote:
On 05/31/2013 10:05 AM, Tsantilas Christos wrote:
On 05/27/2013 07:12 PM, Alex Rousskov wrote:
On 05/27/2013 04:54 AM, Tsantilas Christos wrote:
On 05/26/2013 10:05 PM, Kinkie wrote:
The only thing I
On 06/02/2013 05:35 AM, Amos Jeffries wrote:
On 29/05/2013 8:59 p.m., Tsantilas Christos wrote:
When Squid sends errors to the certificate validation daemon, the daemon
cannot tell which certificate caused which error. This is especially bad
because the validator has to return that same
On 06/02/2013 06:43 AM, Amos Jeffries wrote:
On 1/06/2013 5:14 a.m., Alex Rousskov wrote:
Stepping back a little, I think there are two big problems with the URL
scheme-like approaches (file:, db:, etc.):
1) They combine the method of access (local file, HTTP, database query,
etc.) with the
In summary we seem to be talking about different features here.
1) the syntax for linking access method and location.
* this seems to be agreed as : in URI-style.
2) whether and how add a new parameter, which is syntactically valid
anywhere and tokens are read 1-per-line from that source.
On 4/06/2013 12:40 a.m., Tsantilas Christos wrote:
On 06/02/2013 02:35 PM, Amos Jeffries wrote:
On 29/05/2013 8:59 p.m., Tsantilas Christos wrote:
When Squid sends errors to the certificate validation daemon, the daemon
cannot tell which certificate caused which error. This is especially bad
