Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCSP Responder doesn't work right for paths other than "/" #387

Open
jsha opened this issue Oct 12, 2015 · 0 comments
Open

OCSP Responder doesn't work right for paths other than "/" #387

jsha opened this issue Oct 12, 2015 · 0 comments
Labels

Comments

@jsha
Copy link
Contributor

jsha commented Oct 12, 2015

In a recent pull request, I modified the OCSP Responder's GET path to expect no "/" at the beginning. That means that if your OCSP URLs start with "/ocsp", you'd want to do something like:

http.StripPrefix("/ocsp/", ocspHandler)

That works properly for GET, but since POST requests go to /ocsp instead of /ocsp/, the StripPrefix would return 404 for POSTs. Fortunately, if you OCSP URLs are just /, things work fine.

I created this bug, so I'll work on fixing it. Just filing it here to keep track.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants