[
https://issues.apache.org/jira/browse/TS-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252191#comment-14252191
]
Leif Hedstrom commented on TS-3186:
-----------------------------------
Right. simple is fine. Picking the right place / format wouldn't defeat
simplicity I think? I didn't ask to implement every possible feature :).
The real question is if we make a choice to store this in records.config in a
specific format, then changing it later is much more complicated. So, I really
think you should at least think about if this is the right solution / place for
this, such that we don't have to change it in an incompatible way later. If we
keep it in records.config, a future change to support multiple proxies would be
easy. But, if you decide later that it's necessary to do this different based
on the certificate, then clearly records.config is not the right place.
Just my $.01.
> support ocsp queries through a proxy
> -------------------------------------
>
> Key: TS-3186
> URL: https://issues.apache.org/jira/browse/TS-3186
> Project: Traffic Server
> Issue Type: Improvement
> Components: SSL
> Reporter: Atsutomo Kotani
> Assignee: Alan M. Carroll
> Fix For: 5.3.0
>
> Attachments: ocsp_proxy.diff
>
>
> When ATS behind http proxy, it need ocsp queries through http proxy for ocsp
> stapling.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
