mod-wsgi

I am trying to determine why authentication for protected resources using the Authorization: header behaves properly when using a local development server but not on my deployed apache 2.2 w/mod_wsgi implementation. I am using django 1.8 with django-rest-framework and the django-rest-framework-jwt lib for JWT based authentication. The apache server is ver 2.2 with mod_wsgi. This is all running on an ubuntu 12.04 instance (python 2.7). Working case with manage.py runserver on localhost: # manage.py runserver is running curl -s -X POST \ -d '{"username":"test@test.com", "password":}' \ http:/

I'm getting this in my error logs: ImportError: No module named flask It looks exactly like in Django + mod_wsgi + apache: ImportError at / No module named djproj.urls , but I tried that solution, and it doesn't seem to work... I am correctly inserting the app home and parent folder into the system path, but this error is still coming up. Navigating to my page still brings up the 500 page. More information: I'm using Amazon EC2 free tier, with Apache in the form of httpd. Everything is installed correctly, I'm pretty sure... Here's my stuff (app name badassery and app home folder name hatemail

I am trying to deploy my first Django project on my webserver. I am both new to server configuration and Django so I have a hard time finding my errors. In most tutorials I have seen online, the Django project on the production server is created in /var/www/myproject - however, the Django documentation recommends putting the code outside of /var/www/ for security reasons (see: https://docs.djangoproject.com/en/1.9/intro/tutorial01/ ). So, I put my Django project in a subdirectory of my home folder, which is not accessible to Apache. I added no file to /var/www as no tutorial mentions that this

I got something unusual when developing a small web server using Python2.7+Apache+mod_wsgi . The main usage of this server is: Receiving regular requests from another server(server A), and put the request body into DB. Using some background threads to parse the request body in DB and send the parsed information to a third server(server B). Apache is configured as Windows 'winnt' MPM mode. Code of dispatch.py, which is the entry point, is like below: from urlparse import parse_qs pool = MyThreadClass() # A customized thread class to parse request body in DB pool.start() def application(environ,

I am trying to run webapp2 under Python with Apache and mod_wsgi - specifically: Wampserver for Windows 7 with Apache 2.2.22. So far, I have failed miserably. :-( I used the following example from https://developers.google.com/appengine/docs/python/gettingstartedpython27/usingwebapp : import webapp2 class MainPage(webapp2.RequestHandler): def get(self): self.response.headers['Content-Type'] = 'text/plain' self.response.out.write('Hello, webapp World!') app = webapp2.WSGIApplication([('/', MainPage)], debug=True) When I save this file as c:wamp\www\Python\hello.py , and browse to localhost

I am trying to upload several files in django. On my local maching where I use the djangos build in server everything works fine but on my productivity server I get this error: [Errno 13] Permission denied: '/static' There are many questions about this issue but nothing I found worked for me. In my case it has nothing to do with file permissions. I found out that the problem is that django want save the files in the root folder of my filesystem and not in the root folder of my website. If I create the folder in '/static' the files will be created there but images for example are not shown on

I'm developing a Django site. I'm making all my changes on the live server, just because it's easier that way. The problem is, every now and then it seems to like to cache one of the *.py files I'm working on. Sometimes if I hit refresh a lot, it will switch back and forth between an older version of the page, and a newer version. My set up is more or less like what's described in the Django tutorials: http://docs.djangoproject.com/en/dev/howto/deployment/modwsgi/#howto-deployment-modwsgi I'm guessing it's doing this because it's firing up multiple instances of of the WSGI handler, and