You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I'm aware this probably does not imply a behavioral change in flask_accepts, it is probably the quickest way for me to get to the bottom of this and potentially contribute some documentation here.
if gunicorn serves this project, swagger will accept cookies specified as
cookie * string (header)
if nginx serves this project, the following error occurs: { "errors": { "cookie": "Missing required parameter in the HTTP headers" }, "message": "Input payload validation failed" }
I'm aware of such differences in servers as underscores in variable names not being accepted by nginx but being accepted by various development servers, for example. Is something similar going on here? It seems good to document this in the case that someone wants to use flask_accepts in a production, nginx-driven environment. I'm happy to 1. document a solution 2. be wrong and told why what I'm doing is a bad idea, and what a better one is!
The text was updated successfully, but these errors were encountered:
While I'm aware this probably does not imply a behavioral change in flask_accepts, it is probably the quickest way for me to get to the bottom of this and potentially contribute some documentation here.
Consider this decorator on a post endpoint:
@accepts( {'name': 'cookie', 'type': str, 'required': True, 'location': 'headers'} ) ...
if gunicorn serves this project, swagger will accept cookies specified as
cookie * string (header)
if nginx serves this project, the following error occurs:
{ "errors": { "cookie": "Missing required parameter in the HTTP headers" }, "message": "Input payload validation failed" }
I'm aware of such differences in servers as underscores in variable names not being accepted by nginx but being accepted by various development servers, for example. Is something similar going on here? It seems good to document this in the case that someone wants to use flask_accepts in a production, nginx-driven environment. I'm happy to 1. document a solution 2. be wrong and told why what I'm doing is a bad idea, and what a better one is!
The text was updated successfully, but these errors were encountered: