Re: Flatpages incorrect 302 to 404

As far as I know I constructed the urls properly. For example one of them was /policy/ (that's how it looked in flatpages). I did find another work around though. I removed the flatpages middleware from my settings. And then I added this to my urls: urlpatterns += patterns('',

Re: Flatpages incorrect 302 to 404

2010/9/27 Josh : > bump.  Does anyone have any ideas? Trailing slash issue? Just look into the middleware and see when the response code is modified. Regards, Piotr -- You received this message because you are subscribed to the Google Groups "Django users" group. To post

Re: Flatpages incorrect 302 to 404

bump. Does anyone have any ideas? On Sep 24, 3:56 pm, Josh wrote: > I have a django project, its a satchmo store.  I have noticed that > when the flatpages middleware is in my settings.py 404s seem to be > handled incorrectly.  i.e. if a page really does not exist the server

Flatpages incorrect 302 to 404

I have a django project, its a satchmo store. I have noticed that when the flatpages middleware is in my settings.py 404s seem to be handled incorrectly. i.e. if a page really does not exist the server first sends a 302 response, then a 404. When google crawls it only sees the 302 so it thinks