| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
The test was flawed in that it assumed that the body_file would be
replaced with FakeCGIBody.
|
| |
|
|
|
|
|
|
| |
FakeCGIBody mangles anything that isn't actually form-encoded, such as
JSON that isn't sent with the appropriate content type.
We hereby remove the usage of FakeCGIBody and instead just make the body
itself seekable.
|
| |
|
|
| |
See https://github.com/Pylons/webob/issues/149 for more details.
|
| | |
|
| |\
| |
| | |
request: read body from file if the method is PATCH
|
| | |
| |
| |
| |
| |
| | |
Currently Request.from_file ignore the body of a request if the method
is PATCH. This fixes that by using the dictionary we have to know if a
request might have a body or not.
|
| |\ \
| | |
| | | |
Include a patch from CPython's bug tracker to fix cgi.FieldStorage on 3.x < 3.4.4
|
| |/ / |
|
| |\ \
| | |
| | |
| | | |
Fixes #166, #171
|
| | | |
| | |
| | |
| | |
| | | |
We want to provide people an easy to find resource on what is now going
to be valid in a WebOb cookie.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Sets up the cookies._should_raise using a module setup/teardown
functions instead of setting it at module scope per suggestions from
Michael Merickel.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This makes the warning more noticeable to people and will be less likely
to be ignored.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Someday we can get rid of this mess and just be strict about what we
send, but until such a day we want to warn people that it is going to
happen in the future.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
We want to make sure we have at least one test for CookieProfile that
fetches a cookie from our request object, and then verifies it returns
the appropriate answer.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
WebOb will now raise a ValueError if an attempt is made to set the
cookie to an invalid value. According to RFC6265 a cookie-octet has a
specific subset of allowed ASCII characters, and that subset does not
change whether the value is DQUOT'ed or not.
WebOb will still accept all other cookies, it just won't be able to
create them.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
The previous standard was the JSON serializer, however with upcoming
changes that limit what characters are allowed in cookies, bare JSON no
longer worked because it could return values that are invalid to be
stored in cookies.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Unicode values in cookies are invalid.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
We need to document that max_age can be an integer, timedelta or None,
and what that means.
max_age takes precedence over an expires argument.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Start using the make_cookie call that is available in webob.cookies,
this way we don't duplicate the same behavior.
There are a couple of backwards compatible fixes:
- If expires is set to a timedelta, and max_age is not set, we set
max_age to expires a timedelta
- expires can also be a datetime, however this was not documented. So
if it is a datetime, we want to get a timedelta, by taking the
existing expires value, and removing datetime.utcnow() from the
value.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The documentation erroneously states that that expires can be a
datetime.timedelta, this is incorrect, but since it has been documented
as such, we should continue accepting it.
Add the fact that it can be a datetime.datetime, and probably should be.
|
| | | |
| | |
| | |
| | |
| | | |
The documentation for expires incorrectly states that expires can be a
timedelta, let's add a test for that.
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This makes sure that the header extracted with Response.from_file are
latin1 encoded str instances.
Fixes #99
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Make sure that header names extracted with Response.from_file are `str`
instances otherwise most WSGI implementations will reject the response.
Should fix issue https://github.com/Pylons/webob/issues/99
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \ |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
the tests and code clearly expect (req, app, **kw) and it makes sense that it
would be that way since req is the ephemeral argument and the rest are
defined at setup-time. The documented order before was (app, req, **kw)
which puts the req in-between multiple config arguments in the
signature.
fixes #25, #120
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes the Auth-Param header to remove bad white space in accordance with
RFC7235.
Closes #159
|
| | |/ / / |
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | | |
Closes #189
|
| |/ / / |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
[ci skip].
|