atom feed shows a wrong URL when using apache with mod_proxy

[Michele Azzolari]

Setup: I have a virtual host for media.macno.org and I use
mod\_proxy to access my mediagoblin server (which listen on
127.0.0.1:6543)

Issue: atom feed self link uses a wrong url

For example requesting
`http://media.macno.org/u/macno/atom/ <http://media.macno.org/u/macno/atom/>`_
returns

[Michele Azzolari]

Fixed enabling the ProxyPreserveHost directive on Apache

::

    Alias /mgoblin_media "/var/www/media.macno.org/user_dev/media/public/"   
        Alias /mgoblin_static "/var/www/media.macno.org/mediagoblin/static/"
    
    ProxyPreserveHost On  
        ProxyPass /mgoblin_static/ !  
        ProxyPass /mgoblin_media/ !  
        ProxyPass / [http://127.0.0.1:6543/](http://127.0.0.1:6543/)  
        ProxyPassReverse / [http://127.0.0.1:6543/](http://127.0.0.1:6543/)

[Elrond]

Hi Michele,

I have assigned this bug to you. :)
If you don't like that, just undo it.

If you have the time and fun, you could create a new section on
your setup at
`http://wiki.mediagoblin.org/Deployment <http://wiki.mediagoblin.org/Deployment>`_
which would be great.

[Will Kahn-Greene]

The original url for this bug was ​http://bugs.foocorp.net/issues/725 .

[Christopher Allan Webber]

I don't believe this bug is being presently worked on so I'm removing ownership!

[Ben Sturmfels]

In my experience the Atom feeds work correctly when using Nginx as a reverse proxy. This suggests that the issue here was just related to configuring Apache to pass through relevant headers, not a bug in MediaGoblin.

Since Apache mod_proxy is a less common approach to deployment, it's probably not worth attempting to document this. I'm going to be bold and close this ticket. If I've missed something, please don't hesitate to reopen the ticket.

(I would have preferred a resolution status of "no action". "Invalid" sounds unnecessarily aggressive.)