fredag 9 augusti 2024 kl. 17:05:43 UTC+2 skrev moba...@gmail.com: After a lot of digging and testing...
I setup a test repo with no authetication and got the same result. Image files where blocked. Thanks to the hint from Daniel I looked closer at the config of the nginx reverse proxy. The logs did not really help, so I did a lot try and error. At the end, I found out, I had the option "cache assets" active. If it is on, images will not work, as they are tried to get served by nginx instead I guess. Just as a note: I enabled this option, as I have a second vhost setup with the same ssl certificate, so I wanted the cache. I disabled this option and back to work. Thanks a lot for the help! Thanks for reporting back, it always helps. Bwt: The Subversion project (https://subversion.apache.org/faq.html#reverseproxy) would like to have a configuration sample for a reverse proxy on Nginx, and "don't do this" also helps. Would you consider contributing? Send it to d...@subversion.apache.org Cheers, Daniel Sahlberg Kind regards Juergen daniel.l...@gmail.com schrieb am Freitag, 9. August 2024 um 15:04:01 UTC+2: fredag 9 augusti 2024 kl. 15:01:54 UTC+2 skrev moba...@gmail.com: yes, my apache svn server is running behind a reverse proxy. I use nginx proxy manager. Ich cheked the setup and i see nothing that points out to block image files or so on the reverse proxy. Also looking throught the manuals, I found nothing special I have to setup to make it work. Specially other files, even binary ones, work fine, i can add them, commit them, update and so on. If I have a configuration issue on the reverse proxy, shouldn't I have an issue with all file types then ? And yes, I use path base authorization. But if I can use txt files in the same folder where image files do not work, could this be an issue ? I could try and setup an open world svn repo and run some tests. Any more hints where to look at? nginx logs and configuration. Since you say that the Apache Httpd logs indicate "the image file is blocked before it reaches mod_dav_svn", then I would suppose something in nginx is returning the 401 error which causes TortoiseSVN to ask for login/password. Kind regards, Daniel Kind regards Juergen daniel.l...@gmail.com schrieb am Freitag, 9. August 2024 um 13:42:36 UTC+2: fredag 9 augusti 2024 kl. 12:59:00 UTC+2 skrev moba...@gmail.com: hope anyone can help me track this issue down. I alsodon't know if this is a tortoisesvn issue or a apache issue. I have an Apache SVN server. Use tortoise SVN to commit/add, just daily work. I can add and commit "normal files" like text or zip files just fine. But whenever I try to commit a image flie like "picture.png" or "picture.jpg", tortoise instantly ask me for login details. Giving the right credentials does not help. If I change a text file in the same folder (new or existing), I can commit it without being asked for my login details. I also tried other svn clients, with no change. Enabled extended loging in Apache, but it seems, the commit with the image file is blocked before it reaches mod_dav_svn. If I give to many logins, I get a message in apaches logfile, stating, login failes with wrong password. And I 100% sure, the password is correct. I am a bit out of options, where to look next. Again this only seems to affect image files. Any hints are welcome. It sounds very much like you have a proxy or reverse proxy between you and the SVN server. Or maybe that you have some configuration in Apache httpd that is denying access for certain file names (don't know if that is possible...) or using path based authorization ( https://svnbook.red-bean.com/en/1.7/svn.serverconfig.pathbasedauthz.html). Kind regards, Daniel -- 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/e830c6cf-dcdc-4e5d-9cf8-afe618d7efa6n%40googlegroups.com.
