Proposal #1 sounds reasonable to me, although I would say that any CC header
should take effect when enabled == 1, not just max-age but also any sort of
no-store or similar "don't caching" value. (Maybe that is what you already
meant.) I could also see having min and max lifetime values which
> 在 2015年1月28日,下午11:48,Bardwell, William 写道:
>
> Proposal #1 sounds reasonable to me, although I would say that any CC header
> should take effect when enabled == 1, not just max-age but also any sort of
> no-store or similar "don't caching" value. (Maybe that is what you already
> meant.)
Brian,
Yes it makes perfect sense. But when I saw the virtual run() l I thought I
might me missing something.
Getter will do the trick. For now I will implement my own.
Sandeep.
On Tue, Jan 27, 2015 at 10:03 PM, Brian Geffon
wrote:
> Unfortunately you cannot access the state_ member because it
GitHub user jacksontj opened a pull request:
https://github.com/apache/trafficserver/pull/165
Add some tests around https certificate selection
Primarily around certificate loading since there were some questions
brought up in #121
You can merge this pull request into a Git reposit
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/165
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user jacksontj opened a pull request:
https://github.com/apache/trafficserver/pull/166
Additional new_tsqa tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jacksontj/trafficserver master_tests
Alternatively you can r
Hi Susan,
Is it so, that TS_SSL_CERT_HOOK will (could?) be also called for
server certificates inside ServerHello handler?
In this case ATS, being a SSL proxy, could provide a way to validate
server certs chain and prevent a MITM attack if browser (for example)
has 3rd party Root CA installed.
-