I’ve an https certificate on my openSuSE front-end server.
There I’m redirecting https://www.pluimers.com/continuaci to the internal server (http://192.168.71.46:8080)
But this fails as ContinuaCI emits all URLs in the responses as absolute URLs. This happens right from the start, as http://192.168.71.46:8080 to http://192.168.71.46:8080/account/login?ReturnUrl=%2f which then becomes https://www.pluimers.com/account/login?ReturnUrl=%2f and is not availble.
This is the situation described in http://serverfault.com/questions/561892/how-to-handle-relative-urls-correctly-with-a-reverse-proxy
The easiest two ways to solve this would be to:
1- be able to set the root URL of the Continua CI server
2- be able to configure Continua CI only to emit relative URLs (preferred)
Other solutions (like URL rewriting) are convoluted and therefore really not preferred.
How can I do 1? If not: can 2 be put on the back-log?
I’ve worked around this, but it was quite a bit of work to get https://continuaci.pluimers.com going:
- request a new StartSSL Class 1 certificate for the subdomain continuaci.pluimers.com
- create new vhosts content for HTTPS and HTTP
- configure new virtual hosts for the HTTPS and HTTP in Apache
- mess with the apache configuration so httpd2 pre-check would succeed (that’s an issue in OpenSuSE I still need to research and report)
- fiddler with ProxyPass configuration so it would work
It works (:
Which I need for https://github.com/jpluimers/Conferences/tree/master/2015/20151020-DAPUG-Denmark-Nyborg-Hotel-Hesselet
Hi Jeroen
I’ve been looking at what urls Continua CI produce, and the only absolute urls I’m seeing are external links (like to the help or our website). Continua CI is uses asp.net mvc (v4 currently), and we got to great lengths to make sure all emitted urls are relative. Are you able to point to where these absolute urls are?
Ok, I think I understand what the issue is… the generated urls do not have ~ at the start, not sure if there is a way to make asp.net mvc generate urls that way or not. We’ll investigate, but I would imagine it would be a huge job to review the entire app for this. From my googling, the general consensis is to use subdomains, so you are on the right path imho.
Posted By Vincent Parrett on 14 Oct 2015 05:02 PM
Ok, I think I understand what the issue is.. the generated urls do not have ~ at the start, not sure if there is a way to make asp.net mvc generate urls that way or not. We'll investigate, but I would imagine it would be a huge job to review the entire app for this. From my googling, the general consensis is to use subdomains, so you are on the right path imho.
I think you nailed it with the ~ so please put that on the back log with low priority.
I've a setup where I can test with both a subdomain https://continuaci.pluimers.com and a normal domain https://www.pluimers.com/continuaci
So reviewing can be done.
--jeroen