Lev,
I thought the core already did that server cert verification (controlled
by some config setting). If it doesn't it should. I'll track it down
later today or tomorrow.
But even so, offering a plugin hook point on the handshake with the
origin server seems valuable as well. The ssl_cer
GitHub user jacksontj reopened a pull request:
https://github.com/apache/trafficserver/pull/121
Explain ATS's interesting default SSL cert selection criteria
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jacksontj/trafficserver
Github user jacksontj closed the pull request at:
https://github.com/apache/trafficserver/pull/121
---
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 featu
Github user jacksontj commented on the pull request:
https://github.com/apache/trafficserver/pull/121#issuecomment-72078773
@jpeach Now that it's been fixed upstream, this covers what I was going for
---
If your project is set up for it, you can reply to this email and have your
reply
> On Jan 27, 2015, at 9:58 AM, Susan Hinrichs
> wrote:
>
>
> On 1/27/2015 11:12 AM, James Peach wrote:
>>> On Jan 27, 2015, at 8:34 AM, Susan Hinrichs
>>> wrote:
>>>
>>>
>>> On 1/27/2015 10:30 AM, James Peach wrote:
> On Jan 27, 2015, at 8:18 AM, Susan Hinrichs
> wrote:
>
>>
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/121
---
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 asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/166
---
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
On 1/29/2015 1:16 PM, James Peach wrote:
On Jan 27, 2015, at 9:58 AM, Susan Hinrichs
wrote:
On 1/27/2015 11:12 AM, James Peach wrote:
On Jan 27, 2015, at 8:34 AM, Susan Hinrichs
wrote:
On 1/27/2015 10:30 AM, James Peach wrote:
On Jan 27, 2015, at 8:18 AM, Susan Hinrichs
wrote:
Origi
Github user jpeach commented on the pull request:
https://github.com/apache/trafficserver/pull/122#issuecomment-72101354
FWIW for this specific case, you can use the ``sslheaders`` plugin as a
workaround. Put the values you want into HTTP headers, then log those. In fact,
maybe using
Builds and passes regressions on CentOS 6.5 (2.6.32-431.29.2.el6.x86_64) so
+1 from me.
Brian
On Mon, Jan 26, 2015 at 12:36 PM, Phil Sorber wrote:
> Hello All,
>
> I've prepared a release for v4.2.3 (RC0) which is the latest stable
> release in the 4.2.x series. This is the third release in our
10 matches
Mail list logo
