tanks !
the filter urlencode did the trick.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.
On 8 déc, 10:13, Keats wrote:
> hi,
> How i can add it then ?
>
> i was thinking that the problem is "?" because :
It is. Please refer to the relevant RFC: the question mark is a
reserved character used to specify the beginning of a querystring. If
you want it to be part of the url itself, you d
hi,
How i can add it then ?
i was thinking that the problem is "?" because :
works perfectly any other characters in the topic_name part seems to
work and since i'm only using : (.*) i didn't see how it could be an
URL mismatch matter because for me (.*) means match everything ...
thanx.
--
Yo
As I explained in my original email, the URL in your example _DOES
NOT_ end in a slash. It has a query string that ends with a slash
which is _NOT_ the same thing.
Sorry to shout, but I explained it quite clearly before :/
Cheers
Tom
On Tue, Dec 7, 2010 at 3:50 PM, Keats wrote:
> the urlpatter
the urlpattern is :
^'/blabla/topic/(?P\d+)-(?P.*)/$
and i think it's a bug because if you see request URL there is a
slash
and if it was an urlconf problem django would have reply url not
found.
i think the problem is linked to the fact that the test topic ends
with "?" and for some reason django
On Tue, Dec 7, 2010 at 3:26 PM, Keats wrote:
> Hi,
> if you have
> id="addReplyForm" name="addReplyForm">
> ...
>
>
> when the form is submitted, django complains about this :
> Request Method: POST
> Request URL: http://mysite/blabla/topic/reply/114-test%20?/
> Django Version:
6 matches
Mail list logo
