{"push_id":1478665866,"size":1,"distinct_size":1,"ref":"refs/heads/4.1","head":"56ddc47f23611f6e1c8009caf0b67f535a41802c","before":"0eeeb764391490585f690c8b424d9ce2d43e6a9b","commits":[{"sha":"56ddc47f23611f6e1c8009caf0b67f535a41802c","author":{"name":"Frederic BREGIER","email":"27cae8c71299514eb25c5281347286e7b6626ca3@culture.gouv.fr"},"message":"Extends HttpPostRequestEncoder to support all methods except TRACE\n\nMotivation:\n\nIn Netty, currently, the HttpPostRequestEncoder only supports POST, PUT, PATCH and OPTIONS, while the RFC 7231 allows with a warning that GET, HEAD, DELETE and CONNECT use a body too (but not TRACE where it is explicitely not allowed).\nThe RFC in chapter 4.3 says:\n\"A payload within a XXX request message has no defined semantics;\nsending a payload body on a XXX request might cause some existing\nimplementations to reject the request.\"\nwhere XXX can be replaced by one of GET, HEAD, DELETE or CONNECT.\n\nCurrent usages, on particular in REST mode, tend to use those extra HttpMethods for such queries.\n\nSo this PR proposes to remove the current restrictions, leaving only TRACE as explicitely not supported.\n\nModification:\n\nIn the constructor, where the test is done, replacing all by checking only against TRACE, and adding one test to check that all methods are supported or not.\n\nResult:\n\nFixes #6138.","distinct":true,"url":"https://api.github.com/repos/netty/netty/commits/56ddc47f23611f6e1c8009caf0b67f535a41802c"}]}
{"actor":{"display_login":"Scottmitch"}}