On many pages (e.g. Dashboard -> Configure) Octopus generates XHR requests like this:
http://example.tld/api/Spaces-1/projects/experimental%2Fsummaries
There is an encoding of the slash before the “summaries” which leads to errors when reverse_proxying (apache2) to Octopus. IIS seems to be forgiving about the “%2F”, but the reverse proxy isn’t.
Reproducing the error is simple. Just setup an Apache and use this config:
ServerName example.tld
DocumentRoot /var/www/html
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
ProxyRequests Off
ProxyPreserveHost On
ProxyPass / http://1.2.3.4:8084/
ProxyPassReverse / http://1.2.3.4:8084/