Tracebacks on unexpected keyword parameters or NOT ?

Anonymous avatarAnonymous created an issue

The problem comes when you make queryes like localhost/somepage?var=value and you do not have a var parameter on the somepage method. Suppose you have lots of methods like that and you do not want to let tracebacks pop out just by adding a query parameter. So you have to add a keywords parameter on all those methods.

That is a bit uncosistent, so i'm thinking of a config parameter to do the trick. Ofcourse you can make a filter and check what kind of traceback it is and suppress it but that's just ugly.

Any toughts on this?

Reported by ionel

Comments (4)

  1. Anonymous

    Well this is up to the application developer to handle such cases by trapping the error and serving whatever needs to be served. You could define a decorator that makes sure the signature of your handler is respected and either dump the useless parameters or raises your own error message.

    I think we ought to close this issue.

  2. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.