Changes between Version 7 and Version 8 of devserver_and_apache_differences


Ignore:
Timestamp:
02/27/2008 01:35:54 PM (7 years ago)
Author:
ingmar
Comment:

add request.META info, some reformatting of article

Legend:

Unmodified
Added
Removed
Modified
  • devserver_and_apache_differences

    v7 v8  
    55As I run into troubles porting my site, I hear things like "maybe it is because X."  I call this a rumor.  I also hear "Yes, X happens because Y."  If Y supports X, I call it a confirmed rumor.  So onto the rumors.
    66
    7 Rumors
    8 ======
     7== Rumors ==
    98
    109 * Default Apache config does not follow SymLinks, Devserver does.  (There are FollowSymLinks and other options if you need them. http://httpd.apache.org/docs/2.0/mod/core.html#options )
     
    1817 * devserver re-validates model changes automatically. Under apache, the django process has to be restarted to pick up model changes.
    1918
    20 Facts:
     19== Facts ==
    2120
    22 "Note that the Django development server automagically serves admin media files, but this is not the case when you use any other server arrangement." http://www.djangoproject.com/documentation/modpython/#serving-media-files
     21 * "Note that the Django development server automagically serves admin media files, but this is not the case when you use any other server arrangement." http://www.djangoproject.com/documentation/modpython/#serving-media-files
    2322
    24 devserver's current may not be the same as apache's.  so if your view code references files with relitive paths you will have trouble.
     23 * devserver's current may not be the same as apache's.  so if your view code references files with relitive paths you will have trouble.
     24
     25 * some request.META keys are different, e.g. on the devserver the Content-Type is in {{{request.META['CONTENT_TYPE']}}} while on mod_python that key exists but the value is always None and the actual value is in {{{request.META['HTTP_CONTENT_TYPE']}}}
     26
Back to Top