Encoded XHR request on the dashboard

On many pages (e.g. Dashboard -> Configure) Octopus generates XHR requests like this:


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

    ProxyRequests           Off
    ProxyPreserveHost       On
    ProxyPass               /
    ProxyPassReverse        /

Hi Scheinkultur,

Thank you for reaching out and I’m sorry you’ve hit this issue. I will be looking at reproducing this issue on our end and testing some solutions early next week.

If you discover anything else in the meantime that may help identify why the reverse proxy is being so unforgiving, please let me know.



Hi @scheinkultur

Just jumping in for Dane here, but you’re correct here. We did have an issue with this in our older versions of Octopus - this was corrected in 2020.1.21

I hope this helps, and please don’t hesitate to reach out if you have any further questions.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.