Code

Changes between Version 10 and Version 11 of devserver_and_apache_differences


Ignore:
Timestamp:
10/23/09 11:23:42 (5 years ago)
Author:
programmerq
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • devserver_and_apache_differences

    v10 v11  
    99 * 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']}}} 
    1010 
    11  * 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 ) 
     11 * Default Apache config does not follow symbolic links, while the devserver does.  (There are !FollowSymLinks and other options if you need them. http://httpd.apache.org/docs/2.0/mod/core.html#options ) 
    1212 
    1313 * devserver re-validates model changes automatically. Under apache, the django process has to be restarted to pick up model changes. "The development server automatically reloads Python code for each request."  http://www.djangoproject.com/documentation/django-admin/#runserver-optional-port-number-or-ipaddr-port