Tom Wiesing

This issue looks like a duplicate of #1463. For a workaround, see https://github.com/nginx-proxy/nginx-proxy/issues/1463#issuecomment-652351459.

I'm not sure this should be accepted. When configuring http basic authentication, by default I would expect *all* requests to only be forwarded after authentication; that way no data can...

Are nginx-proxy and your nginx container on the same docker network? It could be that this is not related to https at all but a generic connection issue.

To verify your containers you could do something like: ``` docker network inspect -f '{{range .Containers }}{{.Name}} {{end}}' mydomain_default ``` This will print the names of all containers on the...

This is the default nginx behavior. When an unknown host is encountered, nginx either picks the `default_server` to answer requests from or, in the absence of that, the first server...

I first discovered this on my phone (iOS Safari). Steps to reproduce: 0. Ensure that the system-wide dark mode is enabled 1. Open any article, e.g. https://ar5iv.labs.arxiv.org/html/1910.06709 2. Notice that...

Can reproduce this issue, but only on the `linux/amd64` (my server) architecture. This does not happen on `linux/arm64` (my development machine). I also saw the same behavior on go1.23 and...

I encountered the same issue. The following is a terrible workaround that I'm posting in case someone else needs it. This implements `source.NewClient` via reflect, and then passes it to...

I definitely see your point. For the issue I attempted to reduce it to a minimal test case that showed only the concrete problem I encountered. In my actual use...

This issue is extremely frustrating. I am working inside a drupal '.module' file (with lots of legacy code), which does not allow classes. I therefore cannot use any type aliases.