Closed sviridovdy closed 10 months ago
Hi
I found another solution.
The attribute "action" on tag "form" was forced to current request URI. But with a proxy you've got the application URL behind, not the browser URL.
Now the attribute "action" is removed, that means submit will be done to the current browser URL.
Tested in local with Nginx https://aaa sending to Apache http://bbb
Release https://github.com/stephanediondev/elasticsearch-admin/releases/tag/v1.77
I deployed this new version and it works as expected. Thank you for this fix.
As a note until this fix was released we used to modify config/packages/framework.yaml
file by adding
# the IP address (or range) of your proxy
trusted_proxies: '127.0.0.1,REMOTE_ADDR'
# trust *all* "X-Forwarded-*" headers
trusted_headers: ['x-forwarded-for', 'x-forwarded-host', 'x-forwarded-proto', 'x-forwarded-port', 'x-forwarded-prefix']
Hi, is there a way to support X-Forwarded-Proto header when generating response HTML that contains
form
element? Specifically I mean to use matching scheme inaction
attribute. We have this app running behind load balancer/proxy that is doing SSL termination and we are facing problems that even though web site is loaded over httpsaction
attribute onform
elements hashttp://
scheme.