Permalink
Commits on Sep 7, 2011
  1. version 1.1

    maluke committed Sep 7, 2011
Commits on Aug 27, 2011
  1. remove deprecation warnings for .unicode_body / .ubody (most of the c…

    maluke committed Aug 27, 2011
    …ode affected
    
    would *not* really need to be changed anyway)
Commits on Aug 19, 2011
  1. version 1.1rc1

    maluke committed Aug 19, 2011
  2. update news.txt

    maluke committed Aug 19, 2011
Commits on Aug 18, 2011
  1. more tests

    maluke committed Aug 18, 2011
  2. fix test (missing import)

    maluke committed Aug 18, 2011
  3. bring back to 100% test coverage

    maluke committed Aug 18, 2011
  4. * make Response.write much more efficient (https://bitbucket.org/ianb…

    maluke committed Aug 18, 2011
    …/webob/issue/18)
    
    * make sure copying responses does not reset content_length or content_md5 of the
      original (and that of future copies)
    * remove Response._body so the _app_iter is the only representation
    * merge ResponseBodyFile.write and Response.write
Commits on Aug 14, 2011
Commits on Aug 9, 2011
  1. fix test on Jython (did you know that 'abc'.encode('utf-16') produces…

    maluke committed Aug 9, 2011
    … different
    
    strings on Jython and CPython?)
  2. * change del res.body semantics so that it doesn't make the response …

    maluke committed Aug 9, 2011
    …invalid,
    
      but only removes the response body
    * deprecate response.ubody / unicode_body in favour of new .text attribute
      (the old names will be removed in 1.3 or even later)
Commits on Aug 7, 2011
  1. version 1.1b2

    maluke committed Aug 7, 2011
  2. update news

    maluke committed Aug 7, 2011
  3. When the client disconnects while sending request body, most servers …

    maluke committed Aug 7, 2011
    …just start
    
    returning '' from env['wsgi.input'].read(..) and similar.
    This means the apps get truncated requests.
    
    This commit makes req.body_file wrap the input stream in a proxy that detects
    such conditions and raises a DisconnectError exception while reading. This is
    used (and tested) to make sure req.body, req.POST, req.copy() and other request
    methods and properties do not result in truncated request bodies or form
    dictionaries, but raise an error instead.
    
    The tests use actual wsgiref server to send truncated requests to and verify
    that the codition is handled correctly in WebOb.
Commits on Aug 4, 2011
Commits on Jul 30, 2011
  1. syntax typos

    maluke committed Jul 30, 2011
  2. edit depreaction message

    maluke committed Jul 30, 2011
  3. fix test (dict iteration order)

    maluke committed Jul 30, 2011
  4. * make sure that for methods like GET and DELETE, which usually don't…

    maluke committed Jul 30, 2011
    … have a body,
    
      if the body is set, req.is_body_readable actually becomes true
    * fix doctests
Commits on Jul 28, 2011
  1. Remove restrictions on request methods that are allowed to have a body.

    ianb committed Jul 28, 2011
    The HTTP BIS specification indicates that request bodies are generally
    allowed in these cases, though for methods like GET and DELETE they
    have no defined meaning.
    
    http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-15#section-3.3
    
       The presence of a message-body in a request is signaled by the
       inclusion of a Content-Length or Transfer-Encoding header field in
       the request's header fields, even if the request method does not
       define any use for a message-body.  This allows the request message
       framing algorithm to be independent of method semantics.
    
    And for example regarding GET:
    
    http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-15#section-7.3
    
       Bodies on GET requests have no defined semantics.  Note that sending
       a body on a GET request might cause some existing implementations to
       reject the request.