Hello all,
> >
> > I am interested in making these two changes to Django: Setting
> APPEND_SLASH
> > = False and PREPEND_WWW = True.
> >
> > The following links describe what each of these do but do not tell me
> > actually where these sett
On Fri, Aug 10, 2012 at 10:41 AM, JJ Zolper wrote:
> Hello all,
>
> I am interested in making these two changes to Django: Setting APPEND_SLASH
> = False and PREPEND_WWW = True.
>
> The following links describe what each of these do but do not tell me
> actually where the
Hello all,
I am interested in making these two changes to Django: Setting APPEND_SLASH
= False and PREPEND_WWW = True.
The following links describe what each of these do but do not tell me
actually where these settings reside so that I can actually change them:
http://djangobook.com/en/2.0
Hello there, I am trying to use the Django way of testing, but it
somehow does not work together with the PREPEND_WWW setting. All I get
is the 301 status code and no redirect is followed even when follow=True.
from django.test.client import Client
c = Client()
r = c.get('/users/login/
jmat wrote:
>
> > I'm using 1.0
>
> > Is the patch post 1.0 ? I was having a tough time figuring out if
> > that patch was post 1.0 or not on the ticket (I'm probably blind ;)
>
> > APPEND_SLASH is not modified (so it is default True)
>
> > I c
(I'm probably blind ;)
>
> APPEND_SLASH is not modified (so it is default True)
>
> I changed PREPEND_WWW to True but it did not seem to have any
> effect...
>
> I can try the patch if it is a post 1.0 ... haven't had time to go
> chase into the django code to com
I'm using 1.0
Is the patch post 1.0 ? I was having a tough time figuring out if
that patch was post 1.0 or not on the ticket (I'm probably blind ;)
APPEND_SLASH is not modified (so it is default True)
I changed PREPEND_WWW to True but it did not seem to have any
effect...
I can try
Which version of Django are you using? Do you also have APPEND_SLASH set to
true? There was a ticket about this a while back that was fixed (
http://code.djangoproject.com/ticket/9199).
Hope that helps.
Craig
On Mon, Dec 15, 2008 at 11:23 AM, jmat wrote:
>
> Just curious, has anyone else eve
Ok, thanks, I was curious if we use a .htaccess file to do the re-
writing with django, does the file live in the webroot or in the
django application root?
On Dec 15, 12:41 pm, Ross wrote:
> @jmat I have never tried Django's PREPEND_WWW, but it can easily be
> handled by Apache.
@jmat I have never tried Django's PREPEND_WWW, but it can easily be
handled by Apache. Some of the features involving URLs, paths, etc.
are possibly better left to Apache.
Apache has a rewrite guide that has all the information you should
need. I found a good link a while ago with exactly
Just curious, has anyone else ever set this to true and not had it
work?
On Dec 14, 4:05 pm, jmat wrote:
> I set this to true in my settings file but It doesn't seem to be
> getting picked up.
>
> Does this still have issues with some middleware or am I seeing some
> kind of settings reload or c
I set this to true in my settings file but It doesn't seem to be
getting picked up.
Does this still have issues with some middleware or am I seeing some
kind of settings reload or cache issue?
--~--~-~--~~~---~--~~
You received this message because you are subscrib
I've been having problems with unit tests that check the response
status codes of various pages.
When PREPEND_WWW is set to True (as in test and prod), the Django test
client returns a status code of 301 instead of 200 for any requested
url (as dev is set up).
Has anyone figured out a sol
13 matches
Mail list logo
