Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to specific scheme for base url #1197

Closed
danielqsj opened this issue Aug 21, 2017 · 0 comments
Closed

Option to specific scheme for base url #1197

danielqsj opened this issue Aug 21, 2017 · 0 comments

Comments

@danielqsj
Copy link
Contributor

There is a scene:

client <--https--> haproxy (ssl termination) <--http--> nginx ingress controller <--> real server

My configuration is:

ingress.kubernetes.io/rewrite-target: /
ingress.kubernetes.io/add-base-url: "true"

Althrough I can access my server via https://myweb.com/app/, but some assets can not access correctly.
Chrome error is:
Mixed Content: The page at 'https://myweb.com/app/' was loaded over HTTPS, but requested an insecure stylesheet 'http://myweb.com/app/css/style.css'. This request has been blocked; the content must be served over HTTPS.

The reason is haproxy access to nginx ingress controller via http, so the base tag is <head><base href="http://myweb.com/app/">. It is wrong, https is correct.

It is necessary to add a option to specific scheme for base url.

@aledbf @quickwind

@danielqsj danielqsj changed the title Option to not specific scheme for base url Option to specific scheme for base url Aug 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant