måndag 22 juli 2024 kl. 08:53:56 UTC+2 skrev Fritz Otlinghaus:

I added a video of the error to better document whats happening 
https://youtu.be/EM8sNghOL4w

`Can you share some information about your installation? Is there any 
chance you are behind a proxy (or that the server is behind a reverse 
proxy)? There has been similar error messages in the past caused by proxy 
servers mangling the paths.`

We are running behind an nginx proxy with the following config, do you 
think this could cause such a thing, as the url seems broken in the client 
already?

```
                listen 0.0.0.0:443 ssl ;
                listen [::]:443 ssl ;
                listen 0.0.0.0:443 quic ;
                listen [::]:443 quic ;
                http2 on;
                server_name  xxx;
                location /.well-known/acme-challenge {
                        root /var/lib/acme/acme-challenge;
                        auth_basic off;
                }
                ssl_certificate /var/lib/acme/xxx/fullchain.pem;
                ssl_certificate_key /var/lib/acme/xxx/key.pem;
                ssl_trusted_certificate /var/lib/acme/xxx/chain.pem;
                # Do not allow this site to be displayed in iframes
                more_set_headers          "X-Frame-Options: SAMEORIGIN";
                # Do not permit Content-Type sniffing.
                more_set_headers          "X-Content-Type-Options: nosniff";
                # Reenable XSS Filter even when disabled by user
                more_set_headers          "X-XSS-Protection: 1; mode=block";
                # Do not send referrer header when navigating from HTTPS to 
HTTP
                more_set_headers          "Referrer-Policy: 
no-referrer-when-downgrade";
                include 
"/nix/store/jz0dx3b01kc0bibspzl1dxi9hdi5n11b-nginx-error-pages-iis6.conf";
                location / {
                        proxy_pass http://127.0.0.1:3690/;
                        include 
/nix/store/h7yhsdwp7h51cqwpxzp1p80gwgwf04bd-nginx-proxy-headers.conf;
                        set $fixed_destination $http_destination;
                        if ( $http_destination ~* ^https(.*)$ ) {
                                set $fixed_destination http$1;
                        }
                        proxy_set_header Destination $fixed_destination;
                }


I’m quite certain that something is wrong with the Destination header, is 
is probably url encoded when it should not (or the opposite).

I have never used Nginx so I’m not sure what should be done to fix it but 
there is probably some easy solution.

The Subversion project has a faq with reverse proxy configurations for IIS 
and Httpd. It would be nice if we could add Ngonx there as well if you get 
it to work. See 

https://subversion.apache.org/faq.html#reverseproxy

Kind regards
Daniel


 

                location = /.well-known/security.txt {
                        alias 
/nix/store/fscnlbcafyzs4lmh3jv8f3p1cxh5hr1f-security.txt;
                }
                allow 10.64.0.0/12;
                deny all;
```

On Thursday, July 18, 2024 at 4:22:22 PM UTC+2 Fritz Otlinghaus wrote:

thanks for the quick response, everybody is on vacation right now so i can 
not test further, I will get back to you guys on monday.

On Wednesday, July 17, 2024 at 9:55:52 PM UTC+2 Stefan wrote:

just an FYI: a rename has to be committed in one commit. You can not commit 
the add/delete parts separately (unless you have a really, really old 
server version).

-- 
You received this message because you are subscribed to the Google Groups 
"TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tortoisesvn+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tortoisesvn/3ad35256-007e-4c60-9ddc-8e18abce86dbn%40googlegroups.com.

Reply via email to