On Oct 26, 5:25 am, Jonathan Lundell jlund...@pobox.com wrote:
On Oct 25, 2011, at 2:06 PM, Pawel Jasinski wrote:
hi,
thanks! That solved my ~ problem.
Unfortunately for my öäü (chars above 128 and below 255 in latin-1) I
still need to overcome 2 challenges:
1. re.U must be supplied
The validation is done on purpose. We think that allowing special
characters in the path info makes urls less readable and can be cause
of directory traversal attacks (~ specifically).
Massimo
On Oct 25, 6:24 am, Pawel Jasinski pawel.jasin...@gmail.com wrote:
hi all,
I have discovered that
hi,
of directory traversal attacks (~ specifically).
how exactly?
I am talking about arguments and only arguments.
I agree that ~ in case of application/controller/method makes no sense
In case of static agree 100%, but that is different control path.
The arguments are just that, arguments. If
On Oct 25, 2011, at 11:57 AM, Pawel Jasinski pawel.jasin...@gmail.com wrote:
hi,
of directory traversal attacks (~ specifically).
how exactly?
I am talking about arguments and only arguments.
I agree that ~ in case of application/controller/method makes no sense
In case of static
hi,
thanks! That solved my ~ problem.
Unfortunately for my öäü (chars above 128 and below 255 in latin-1) I
still need to overcome 2 challenges:
1. re.U must be supplied to compile or match to take advantage of
unicode interpretation of \w.
I could shift compile into the routes.py. Is it
On Oct 25, 2011, at 2:06 PM, Pawel Jasinski wrote:
hi,
thanks! That solved my ~ problem.
Unfortunately for my öäü (chars above 128 and below 255 in latin-1) I
still need to overcome 2 challenges:
1. re.U must be supplied to compile or match to take advantage of
unicode interpretation
6 matches
Mail list logo
