Bug #417

parameter parsing in webserver

Added by Roman Köhler over 1 year ago. Updated 7 months ago.

Status:Closed Start date:07/11/2010
Priority:(P3) Normal Due date:
Assignee:Roman Köhler % Done:

0%

Category:-
Target version:0.9.0-alpha1
Severity:Normal Target:
Story points-
Velocity based estimate-

Description

there is a problem with parameter parsing (in the eventrequesthandler):

when you what to parse a parameter to the events, you will encode it in the parameter=<URLENCODEDPARAMETER>
the <URLENCODEDPARAMETER> are build as "<eventParameter1>=<value>;<eventParameter2>=<value>" (but already encodes as %3CeventParameter1%3E%3D%3Cvalue%3E%3B%3CeventParameter2%3E%3D%3Cvalue%3E)

now the problem: what if <value> itself must contains a "=" (like "FREQ=DAILY", what must be done for iCal-scheduled-Events: iCalRRule=FREQ=DAILY) so there we need some kind of double-url-encoding or a special rule for pasing a "=" (or a %3D as String) to parameters. maybe parametervalue should be quoted ....
or instead of parameter=iCalRRule=FREQ=DAILY (exactly parameter=iCalRRule%3DFREQ%3DDAILY) make a
paramter_iCalRRule=FREQ%3DDAILY direcly in that call (that would also be more reader-friendly)

Associated revisions

Revision 9362004c
Added by Patrick Stählin over 1 year ago

Handle key-value pairs correctly

Fixes #417

History

Updated by Miguel Rodriguez over 1 year ago

  • Status changed from New to Assigned
  • Assignee set to Patrick Stählin
  • Target version set to 0.9.0-alpha1

Updated by Patrick Stählin over 1 year ago

  • Status changed from Assigned to Resolved
  • Assignee changed from Patrick Stählin to Roman Köhler

Updated by Michael Troß over 1 year ago

  • Status changed from Resolved to Closed

as agreed upon

Also available in: Atom PDF