On Tue, Oct 27, 2009 at 7:38 PM, Joshua Partogi <joshua.part...@gmail.com>wrote:

>
> Hi all,
>
> I keep getting an error from the server because there's a web crawler
> that is crawling at a URL that does not exists on my application
> because it made a guess of a URL that should be on my application.
> This is the error that I get:
>
> NoReverseMatch: Reverse for 'blog-month-archives' with arguments
> '(u'2009', u'10\u6708')' and keyword arguments '{}' not found.
>
> How could this error happen? I mean is my assumption right that the
> web crawler is crawling at a URL that it guesses should be available
> on my app?


Possibly, but note that your app also thinks this URL that has been
requested is valid and supported by your app.  You don't get NoReverseMatch
exceptions from forward URL resolution.  Rather, the requested URL has
resulted in URL resolution finding a view to call to produce a page in
response.  It is that view (or code it calls) that is attempting a reverse
url lookup for  blog-month-archives with the listed arguments.

Is there any way we can stop this from happening? I only
> get this from on web crawler so far. But I'm just concerned that it
> will choke my server if it keeps on doing that.
>
>
This is a wild guess, but it looks like you may have one urlpattern entry
that allows a broad range of values in one element, but then that element is
specified as an argument to a reverse call for a blog-month-archives that
has a more restrictive pattern governing what is acceptable for at least one
(I'd guess the second one, where the value contains a unicode character) of
its arguments.

Karen

--~--~---------~--~----~------------~-------~--~----~
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 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to