Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Support for unmatching context-paths with reverse proxys #16348

@Captain-P-Goldfish

Description

@Captain-P-Goldfish

Description

Please add support for X-Forwarded-Prefix header. This can be used in cases in which the context-path of the reverse proxy differs from keycloaks context-path:

apache2:  https://apache2/keycloak
keycloak: https://keycloak/

which would require the reverse proxy to pass the information about the context-path "/keycloak" to the server

spring for instance does solve this problem by setting the following two configuration params:

# used to resolve the headers:  X-Forwarded-Server, X-Forwarded-Proto, X-Forwarded-Port
server.use-forward-headers=true

# used to resolve the header: X-Forwarded-Prefix
server.forward-headers-strategy=framework

Discussion

No response

Motivation

No response

Details

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions