- Notifications
You must be signed in to change notification settings - Fork43
Case-insensitive HTTP header parsing#34
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
MICHAEL!! |
So, I can merge this but there are no tests and I don't know how to cut a release. You wrote all this I'll trust that it works. As far as cutting a release goes... |
Honestly it's been way too long since I setup a release - I believe you need to bump the version in the |
Justin tried it, we'll see how it goes... ihavenoideawhatiamdoing.jpg |
glensc commentedSep 5, 2019
well. you can typically just |
glensc commentedSep 5, 2019
oh, and thanks for handling this, that promptly, I don't need to use |
glensc commentedSep 5, 2019
and close this one:#24 |
@nate@jgreer I think you guys need to reach out to Packagist and take ownership of the Zencoder packagehttps://packagist.org/packages/zencoder/zencoder-php I'd recommend setting up web hooks on this repo once you have ownership so updates are automatic in the future... |
glensc commentedSep 6, 2019
I think for that need to submit issue to here: i've seen similar transfer requests:
so I think it's best if you can reach out@tblanchard, I'm not sure if that's the same packagist user:https://packagist.org/users/tblanchard/ |
glensc commentedSep 10, 2019
We've reached out regarding this, but may end up needing to wait for Packagist to automatically pick up the new version. I do not know how often it checks. |
glensc commentedSep 10, 2019
glensc commentedSep 16, 2019
2.2.4 appeared now in packagist: I wished someone sent ping here about success :( |
This PR updates the HTTP parsing class to ensure that all HTTP header keys are lowercased before returning the result to the caller. This is in-line with RFC2616 and will be compatible with http/2.