Requisitioning UI fails to load in modern browsers if used behind a proxy

Description

Using apache as reverse proxy adds the following header to each request:

(which is a good thing to do, BTW).

Browsers like chromium and google chrome fails to include and execute the baseref.jsp with the following error:

This leads to some more follow-up errors which renders the new provisioning UI unusable.

To fix this, we should set the correct content for baseref.jsp (and maybe others).

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Alejandro Galue May 2, 2016 at 10:44 AM

Alejandro Galue May 2, 2016 at 10:33 AM

Here is what I'm planning to commit:

Alejandro Galue May 2, 2016 at 10:32 AM

It works!

I'll create a pull request in a few minutes, but if you can give it a try it would be nice, as I don't have a testing environment with a proxy configured.

Alejandro Galue May 2, 2016 at 10:27 AM

I found this:

I'm going to try it.

Alejandro Galue May 2, 2016 at 10:24 AM

Got it.

I'm not sure if we can manipulate the MIME-Type from a JSP. If that's possible and you know how to do it without creating a controller just for that, let me know.

Fixed

Details

Assignee

Reporter

Components

Affects versions

Priority

PagerDuty

Created May 2, 2016 at 7:30 AM
Updated May 6, 2016 at 11:45 AM
Resolved May 6, 2016 at 7:45 AM