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

Handle PUT data #11

Open
wants to merge 32 commits into
base: master
Choose a base branch
from
Open

Handle PUT data #11

wants to merge 32 commits into from

Conversation

CloCkWeRX
Copy link

CloCkWeRX and others added 30 commits January 25, 2012 23:04
As per RFC 5849 section 3.4.1.3.2, parameter names are encoded to form the signature base string. If they are not decoded when the request is parsed, they are double encoded in the base string.
Decode parameter names as well as values in provider.
See https://pear.php.net/bugs/bug.php?id=18431 and
https://pear.php.net/bugs/bug.php?id=20106.

This handles the request body with a consistent API to the way request
headers are handled. It should fix the bugs in both 18431 and 20106.
Use exception chaining if PHP 5.3 is available.
See [PEAR Bug 17806](https://pear.php.net/bugs/bug.php?id=17806)

[RFC 5849 section
3.4.1.3.1](http://tools.ietf.org/html/rfc5849#section-3.4.1.3.1) says
any request can have params in the request body provided the
content-type is set correctly and the entity-body is single-part and
formatted correctly.
Handle HTTP request body params better.
 * Add LICENSE and README as role=doc exceptions
 * Ignore *.tgz
Parameter passed to reset() must be a reference.
Strip the Oauth scheme before parsing parameters. Strip whitespace consistently from parameters. Add comments.
Fix parsing of Authorization header values.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants