raise Response(400) for CRLFInjection #249
Closed
Labels
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 |
pjz
added a commit
that referenced
this issue
Jan 5, 2014
In keeping with our internal response, it's a child object of Response.
chadwhitacre
added a commit
that referenced
this issue
Jan 7, 2014
This avoids a circular import by burying an import rather than folding two files together.
Done in #278! |
Changaco
pushed a commit
that referenced
this issue
Mar 11, 2016
This avoids a circular import by burying an import rather than folding two files together.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: