Steffen Bleul comments

Results 44 comments of


                                            Steffen Bleul

Fixing "Pages with special characters in title are not accessible via reverse proxy" for Confluence

You generated config looks outdated. Have you tried updating the image with `docker pull`?

Fixing "Pages with special characters in title are not accessible via reverse proxy" for Confluence

I would still include the custom config.

Fixing "Pages with special characters in title are not accessible via reverse proxy" for Confluence

Maybe I will take a look. Btw. I am running Confluence fine without synchrony proxy. Latest Confluence version runs synchrony fine over path.

Changes to location regexp broke previously working configs

This had been reported. See here: https://github.com/blacklabelops/nginx/tree/9dfac912fd4281c4efa7a87a48d5a0f6fbafd66a#important-notice

Changes to location regexp broke previously working configs

Same here, does not work at all. Dunno how I tested this.

Changes to location regexp broke previously working configs

Reverse proxy now adding the missing slash.

Changes to location regexp broke previously working configs

Okay checking static files feature.

Changes to location regexp broke previously working configs

I was able to serve static files: ~~~~ docker run -d \ -p 80:80 \ -v $(pwd)/htmltest:/htmltest \ --name nginx \ -e "SERVER1REVERSE_PROXY_LOCATION1=/" \ -e "SERVER1REVERSE_PROXY_APPLICATION1=custom" \ -e "SERVER1REVERSE_PROXY_DIRECTIVE1FIELD1=root /htmltest"...

Still getting errors like "client sent invalid header line: "X_FORWARDED_PROTO: http" while reading client request headers"

Can you please elaborate your problem in more detail? Especially what does `still` mean?

Still getting errors like "client sent invalid header line: "X_FORWARDED_PROTO: http" while reading client request headers"

Fixed.