[Bug 2073515] Re: functionality loss in mod_proxy rewritten path

2024-09-24 Thread Marc Deslauriers
** Changed in: apache2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073515 Title: functionality loss in mod_proxy rewritten path To manage notifications a

[Bug 2073515] Re: functionality loss in mod_proxy rewritten path

2024-07-23 Thread Daniele Gozzi
Yes, that is the first problem we are getting. It is probably introduced by the "add root prefix: asd.example.com/ -> /asd.example.com/" step. The triple slash is introduced by my last RewriteRule which does not account for a leading slash (RewriteRule ^([^.]+)). My use case with the RewriteRule

[Bug 2073515] Re: functionality loss in mod_proxy rewritten path

2024-07-22 Thread Marc Deslauriers
Thanks, that is very helpful, so we're getting an extra slash here: rewrite '/asd.example.com/' -> 'http:///asd:8000/' instead of: rewrite '/asd.example.com/' -> 'http://asd:8000/' and I can confirm this issue exists with upstream's 2.4.62 release too, so I will keep an eye out for new fixes th

[Bug 2073515] Re: functionality loss in mod_proxy rewritten path

2024-07-22 Thread Daniele Gozzi
Sure. No problem. This should show how adding a leading slash is breaking the last RewriteRule. It would be harder to reproduce Incompatibility #2 as I don't have the FCGI daemon any more, as I'm using an HTTP application server now instead. However, if you need, I could circumvent the #1 incompati

[Bug 2073515] Re: functionality loss in mod_proxy rewritten path

2024-07-22 Thread Marc Deslauriers
I'm having difficulty reproducing your exact issue. Could you please run apache with "rewrite:trace3" and show working and non-working requests from error.log? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launch

[Bug 2073515] Re: functionality loss in mod_proxy rewritten path

2024-07-18 Thread Marc Deslauriers
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073515 Title: functionality loss in mod_proxy rewritten path To manage notifications about

[Bug 2073515] Re: functionality loss in mod_proxy rewritten path

2024-07-18 Thread Marc Deslauriers
Thanks for reporting these issues. There are been a few regression fixes upstream following the security updates from their 2.4.60, 2.4.61 and 2.4.62 releases. I will attempt to reproduce your issue and see if it has been fixed upstream yet. ** Changed in: apache2 (Ubuntu) Assignee: (unassign