Hi Jonathan, On Jan 27, 12:04 am, Jonathan Lundell <jlund...@pobox.com> wrote: > This applies to both the old and new URL rewrite paths, regardless of whether > there's any rewriting going on. > > Previously, a trailing slash after args would cause an extra arg to be added > to the list with a value of '' (empty string). In the old logic, an embedded > empty arg was illegal. > > That is: > > /a/c/f/arg1 > > gave args as ['arg1'] > > /a/c/f/arg1/ > > gave args as ['arg1', ''] > > /a/c/f/arg1//arg2 > > was illegal. > > Now, trailing slashes are stripped, so the first two examples about give > ['arg1'], as does /a/c/f/arg1/////
Maybe that should be parsed as ['arg1', '', '', '', ''] > Also, embedded empty args are legal, so the arg2 example above yields ['', > 'arg2'] Did you mean ['arg1', '', 'arg2'] ? I have not checked, but are those series of slashes legal according to an RFC?. Denes. On Jan 27, 12:04 am, Jonathan Lundell <jlund...@pobox.com> wrote: > This applies to both the old and new URL rewrite paths, regardless of whether > there's any rewriting going on. > > Previously, a trailing slash after args would cause an extra arg to be added > to the list with a value of '' (empty string). In the old logic, an embedded > empty arg was illegal. > > That is: > > /a/c/f/arg1 > > gave args as ['arg1'] > > /a/c/f/arg1/ > > gave args as ['arg1', ''] > > /a/c/f/arg1//arg2 > > was illegal. > > Now, trailing slashes are stripped, so the first two examples about give > ['arg1'], as does /a/c/f/arg1///// > > Also, embedded empty args are legal, so the arg2 example above yields ['', > 'arg2']
