I wrote:
It looks like something is caching the 301 response.
Nope - it was my own stupidity!
A few months back there were a couple of different people creating content
off-site and they wanted to include images in the templates. In the interests of
expediency I let them use relative paths to the images as long as they were at
or below the current template directory. Then I added a StaticURLParser to my
middleware.py that pointed to the 'templates/docs' directory, which let the
images be accessed w/o requiring code changes or moving them around after
uploading from the off-site content creators (i.e. via webdav). This worked ok
until this latest Pylons update, which broke this big hack :-/ (although I'm not
sure what change actually caused the breakage).
Darn that expediency :-)
Robert
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" 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/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
