summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* optimize tracking of pending outbuf bytesfix-deadlock-on-disconnectMichael Merickel2019-04-022-19/+23
|
* switch to an RLock as handle_close is called sometimes during _flush_someMichael Merickel2019-04-021-10/+5
|
* add changelog for #241Michael Merickel2019-04-021-0/+1
|
* fix a deadlock when the client disconnects while flushing dataMichael Merickel2019-04-021-6/+10
|
* back-sign the claMichael Merickel2019-03-291-0/+2
|
* Merge pull request #240 from Pylons/error-task-disconnectBert JW Regeer2019-03-283-1/+32
|\ | | | | handle client disconnections while rendering task error
| * handle client disconnections while rendering error responseerror-task-disconnectMichael Merickel2019-03-283-1/+32
|/
* Merge pull request #239 from Pylons/close-outbufsBert JW Regeer2019-03-282-7/+19
|\ | | | | fix potential race condition when a socket closes unexpectedly
| * fix potential race condition when a socket closes unexpectedlyclose-outbufsMichael Merickel2019-03-272-7/+19
|/
* Merge pull request #238 from Pylons/close-app-iter-on-disconnectBert JW Regeer2019-03-274-19/+72
|\ | | | | interrupt the app_iter if it tries to write to a closed socket
| * remove threading commentclose-app-iter-on-disconnectMichael Merickel2019-03-261-2/+0
| |
| * close the buffer if a write fails before the channel takes over handling itMichael Merickel2019-03-261-19/+19
| |
| * interrupt the app_iter if it tries to write to a closed socketMichael Merickel2019-03-263-0/+55
| |
* | Merge pull request #237 from Pylons/update-toxBert JW Regeer2019-03-272-21/+15
|\ \ | |/ |/| use tox extras key for testing and add pypy3
| * use tox extras key for testing and add pypy3update-toxMichael Merickel2019-03-252-21/+15
|/
* Prep v1.2.1v1.2.1Bert JW Regeer2019-01-252-1/+15
|
* Merge pull request #232 from Pylons/fix/remote_addrBert JW Regeer2019-01-252-8/+18
|\ | | | | Fix: REMOTE_ADDR IPv6 representation
| * Update tests to remote brackets from REMOTE_ADDRBert JW Regeer2019-01-251-4/+5
| |
| * Strip brackets from REMOTE_ADDR for IPv6Bert JW Regeer2019-01-251-2/+7
| |
| * Before adding brackets, verify it's not an IPv4 addressBert JW Regeer2019-01-251-2/+6
|/
* Prep for 1.2.0v1.2.0Bert JW Regeer2019-01-142-1/+9
|
* Prep for v1.2.0b3v1.2.0b3Bert JW Regeer2019-01-072-3/+3
|
* Remove unnecessary strip()Bert JW Regeer2019-01-071-2/+0
|
* add changelog for #228Michael Merickel2019-01-041-2/+12
|
* Merge pull request #228 from Pylons/proxy-updatesBert JW Regeer2019-01-044-20/+36
|\ | | | | fix a few proxy issues after testing in production
| * minor docs tweak on reverse proxy setupproxy-updatesMichael Merickel2019-01-031-3/+3
| |
| * error if trusted_proxy_count is set without trusted_proxyMichael Merickel2019-01-032-5/+28
| |
| * simplify conditional when clearing untrusted headersMichael Merickel2019-01-031-1/+1
| |
| * fix docs to not support comma-separated settingsMichael Merickel2019-01-031-1/+1
| | | | | | | | fixes #225
| * allow clear_untrusted_proxy_headers when trusted_proxy is NoneMichael Merickel2019-01-032-11/+4
|/ | | | fixes #227
* fix pastedeploy urlMichael Merickel2019-01-031-1/+1
|
* Prep v1.2.0b2v1.2.0b2Bert JW Regeer2019-01-021-1/+1
|
* Add CHANGES.txtBert JW Regeer2019-01-021-0/+11
|
* Only warn/fake bytes written if there is dataBert JW Regeer2019-01-021-1/+1
|
* Add link to documentationBert JW Regeer2018-12-311-0/+3
|
* FormattingBert JW Regeer2018-12-311-1/+1
|
* Prep 1.2.0b1v1.2.0b1Bert JW Regeer2018-12-311-1/+1
|
* Move history from CHANGES.txtBert JW Regeer2018-12-312-95/+95
|
* Add CHANGES.txt for #224Bert JW Regeer2018-12-311-2/+13
|
* Merge pull request #224 from Estartu/masterBert JW Regeer2018-12-121-1/+1
|\ | | | | added any as valid value for the trusted_proxy adjustable
| * changed any to * as any could potentially be a valid remote_peerGerhard Schmidt2018-12-131-1/+1
| |
| * added any as valid value for the trusted_proxy adjustableGerhard Schmidt2018-12-121-1/+1
|/ | | | | | | | | | | Backgound is when waitress is running inside a container, any request is originates from the gateway of the container network, not from the outside ip. The container network changes every time the container is restarted to a random new network number. So setting one IP as trusted_proxy isn't possible but still needed as most of the time an reverse proxy is between the client an the container. So if it's ensured that only requests from the reverse proxy can reach the container, trusting any host is not a problem.
* Merge pull request #209 from Pylons/bugfix/socket-server-name-portBert JW Regeer2018-12-029-205/+1336
|\ | | | | Use Forwarded/X-Forwarded-{For,Host,By,Port,Proto} to fixup WSGI environ
| * clear untrusted headers if trusted_proxy is set but does not matchMichael Merickel2018-12-022-109/+128
| |
| * fix docs formattingMichael Merickel2018-12-023-82/+120
| |
| * Update CHANGES.txt for #215bugfix/socket-server-name-portBert JW Regeer2018-12-021-0/+5
| |
| * Add note to CHANGES.txt for proxy header supportBert JW Regeer2018-12-021-0/+22
| |
| * Update reverse proxy documentationBert JW Regeer2018-12-021-92/+49
| | | | | | | | Get rid of paste middleware
| * Add documentation for new argumentsBert JW Regeer2018-12-021-2/+77
| |
| * Try harder at getting the WSGI environ rightBert JW Regeer2018-12-022-4/+62
| | | | | | | | When facing the possibility of a proxy that is sending wacky values