Re: [pylons-discuss] waitress - customer headers

thx, now it is clear. Am Mittwoch, 16. Oktober 2019 04:54:17 UTC+2 schrieb Bert JW Regeer: > > This is due to your custom header containing an underscore. > > See https://github.com/Pylons/waitress/issues/194 for more information. > > Bert > > On Oct 15, 2019, at 05:47, 'Roman S' via

Re: [pylons-discuss] waitress - customer headers

This is due to your custom header containing an underscore. See https://github.com/Pylons/waitress/issues/194 for more information. Bert > On Oct 15, 2019, at 05:47, 'Roman S' via pylons-discuss > wrote: > > hi all, > > how do I allow a

Re: [pylons-discuss] waitress - customer headers

If you can see the header in a flask app served with gunicorn but not in the same app using waitress then the answer is likely related to the actual content of the request and header so you probably need to provide a reproducible example. I think the current dummy example you're showing is

[pylons-discuss] waitress - customer headers

hi all, how do I allow a custom header in the request (retrieving it in a simple flask app)? example: curl -X GET --header 'Accept: application/json' --header 'SESSION_DATA: ...c2Vy...' http://localhost:8080/endpoint waitress just ignores the header SESSION_DATA, whereby gunicorn e.g.