New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
raise Response(400) for CRLFInjection #249
Comments
you think? or you think you should insert a translate_CRLFInjection_to_400Response(exc_info) ? |
Ooooh ... I see what you did there. ;-) We need some principle by which we decide what functionality goes in Aspen core and what doesn't, and additionally what gets its own function in the algorithm. A topic for Friday's call, perhaps? |
So what we decided on the call was that we are going to look at using subclasses for all |
In keeping with our internal response, it's a child object of Response.
This avoids a circular import by burying an import rather than folding two files together.
Done in #278! |
This avoids a circular import by burying an import rather than folding two files together.
Right now we raise CRLFInjection if such is detected. It would be helpful from a logging standpoint to be able to class those with other bad user input problems. I propose that CRLFInjection subclass Response and the code is 400.
The text was updated successfully, but these errors were encountered: