| just as a follow up to this, after debugging it with Malcom, we discovered we weren't copy()'ing the extra context parameter when we passed it into the request.
so the previous request was modifying it and we then passed it back into the new one.
On 07/08/2006, at 9:57 AM, Ian Holsman wrote:
On 07/08/2006, at 9:49 AM, Malcolm Tredinnick wrote:
Hey Ian,
On Mon, 2006-08-07 at 09:28 +1000, Ian Holsman wrote: this problem has me stumped.. and i have no idea why this is happening.
[...]
for some reason every once and a while it thinks basepath is another completly different (but valid) URL eg /aggy/tag/play/ which I'm guessing is someone else's request.
I'm getting a headache just thinking about it. You do realise it's first thing Monday morning, right? This isn't a good way to start the week. :-(
yeah.. tell me about it ;(
What's your setup? Apache + mod_python or something else?
apache + mod-python in this instance Apache/2.0.52 (Red Hat) mod_python/3.2.8 Python/2.4.3
Also, if I send a request for /aggy/tag/play/popular, will it get that far in the code? I've seen some very bizarre URLs sent to my weblog that make me think there are (for example) some horribly broken feed readers out there that just don't understand relative URLs *at all*. So is it possible that somebody is just sending a completely bogus path?
nope.. but /aggy/tag/play/ would. it's a valid request.
and this is happening on the page it renders.. it is showing the invalid links *in* the HTML.
it's like the template processor is grabbing some stuff from another request or something weird.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---
|
