2

Here's what my environment looks like:

  • REST api (django), running over WSGI (mod_wsgi) on port http://server:8107/api
  • static files for the API site (i have some admin pages), in a directory, say /opt/wsgi/staticfiles/subdomain
  • Web application (expressjs), running over pm2/nodejs, on http://server:3002/

I need to group all this under a virtualhost on port 80 as follows:

Here is the relevant part of the configuration:

<VirtualHost *:80>

    ServerName subdomain.server
    ServerAlias subdomain.server.local

    Alias /api/static/ /opt/wsgi/staticfiles/subdomain/
    <Directory /opt/wsgi/staticfiles/subdomain/ >
        Order Allow,Deny
        Allow from All
        Options -Indexes
        IndexOptions Charset=UTF-8
    </Directory>

    ProxyPass /api http://127.0.0.1:8107/api
    ProxyPassReverse /api http://127.0.0.1:8107/api

    ProxyPass / http://127.0.0.1:3002/
    ProxyPassReverse / http://127.0.0.1:3002/

</VirtualHost>

Now, when I try to access a static resource (let's say for example /api/static/js/jquery.js) i find that the url is not resolved first by the Alias directive, but rather passed to the WSGI app (/api), which then obviously fires a 404 error.

Re-ordering the directives does not seem to have any effect.

What should I change to ensure HTTPD will serve /api/static before anything else?

*EDIT*: I run Apache HTTPD 2.2.15 under a CentOS 6.5 distro
2

The following conf is what you are looking for :

ProxyPass /api/static !

It tells Apache to not take this path into account when routing stuff to your proxied application, so it can be dealt with other kind of access (here your Alias directive).

1
  • Works like a charm! – Olivier H Aug 24 '16 at 15:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.