incorrect int query params causes zope error

Bug #1044198 reported by Nathan Van Gheem
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zope 2
Invalid
Undecided
Unassigned

Bug Description

You can test on any zope2 install and produce an error: http://plone.org/?b_start:int=20%22'

I suggest if the :int param can't be converted to integer, then it should just be assigned bstart:int = string value.

Revision history for this message
Hanno Schlichting (hannosch) wrote :

I changed the title and removed the "crash" statement. All I get is a simple ValueError with the normal error handling kicking in. The same happens for a number of other converters when presented with invalid input.

I'm not sure I'd change anything here at all. But I'd prefer an explicit exception over some guessing or partial data conversion.

summary: - incorrect int query params causes zope to crash
+ incorrect int query params causes zope error
Changed in zope2:
status: New → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

The zope2 project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope2.

Changed in zope2:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.