You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the nginx config generated by the reverse-proxy abstraction does not properly translate path settings into location entries - in my particular case, I need a trailing slash in the location entry to only match subroutes of a given path.
Expected behaviour:
path = "/api/" generates location /api/
Observed behaviour:
path = "/api/" generates location /api
I didn't check, but there could be more functionality affected by this issue (for example regexes), so the path setting should be translated into the location entry as closely as possible.
The text was updated successfully, but these errors were encountered:
Fixed in 211b0a3.
Leaving this open for @qknight to think about implications of this change, for example the previous removal of double slashes in the path being disabled.
Currently, the
nginx
config generated by thereverse-proxy
abstraction does not properly translatepath
settings intolocation
entries - in my particular case, I need a trailing slash in thelocation
entry to only match subroutes of a given path.Expected behaviour:
path = "/api/"
generateslocation /api/
Observed behaviour:
path = "/api/"
generateslocation /api
I didn't check, but there could be more functionality affected by this issue (for example regexes), so the
path
setting should be translated into thelocation
entry as closely as possible.The text was updated successfully, but these errors were encountered: