Marty Alchin wrote: > Also, though, I have to ask why you're using such a complicated URL > pattern in the first place? For some applications, I can understand > accepting a full URL, but your pattern is expecting something very > specific, which means you're not looking to accept just any arbitrary > URL. Why bother using the full URL at all then? Couldn't you just > append a portion of it instead, and infer the rest in your code? If > you're after a full, arbitrary URL, your regex is far too specific at > this point.
The OP's trying to implement http://oembed.com/, but missed that the part that starts with a "?" is a URI query. Such queries are parsed by Django and are passed to the views via special QueryDict attributes; see: http://www.djangoproject.com/documentation/request_response/ for details. </F> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
