Github user jacksontj commented on the pull request:
https://github.com/apache/trafficserver/pull/192#issuecomment-119040683
We've been doing that for all of the tests actually. In my tests at least
I'm not verifying the validity of the cert-- since I can check to make sure
its the exact one that I want. This saves some CPU for the test boxes, and
more importantly removes a moving part for the tests.
On Mon, Jul 6, 2015 at 12:26 PM, repodude <notificati...@github.com> wrote:
> Hey Feifei,
>
> I'm curious why are we incorporating a static pre-generated certificate,
> rather than, perhaps a script that just generates one to be used for
> testing.
>
> One issue I see with incorporating a static test cert is the expiration
> time. The ones in this patch expire April 29, 2016.
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/trafficserver/pull/192#issuecomment-118970165>.
>
---
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 is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
