[Bug 63263] New: New issue appeared after update, ServerName directive was not set
https://bz.apache.org/bugzilla/show_bug.cgi?id=63263 Bug ID: 63263 Summary: New issue appeared after update, ServerName directive was not set Product: Apache httpd-2 Version: 2.4.6 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: Core Assignee: bugs@httpd.apache.org Reporter: hossea...@gmail.com Target Milestone: --- I was able to figure out a problem in my site which was using virtualhost. I had my main domain in a virtualhost and `ServerName` attribute at root was commented out. After update my main domain did not link to the same RootDocument as before. After some trouble-shooting I thought the update may messed with the rules. Probably a new feature is active in v2.4.6 that looks for domain name associated with the running server and uses it as `ServerName`. If I'm right. Then this issue may result issues for others too. For those who have the same problem as me. Simply add ServerName at root with ipv4 address and port 80. To avoid auto-detection. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
[Bug 63095] invalid html tag in blancer manager ( ">" missing )
https://bz.apache.org/bugzilla/show_bug.cgi?id=63095 Christophe JAILLET changed: What|Removed |Added Keywords||FixedInTrunk -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
[Bug 63095] invalid html tag in blancer manager ( ">" missing )
https://bz.apache.org/bugzilla/show_bug.cgi?id=63095 Christophe JAILLET changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Christophe JAILLET --- Hi, Thx for the report. It has been fixed in r1855614 with another small HTML syntax issue. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
[Bug 63095] invalid html tag in blancer manager ( ">" missing )
https://bz.apache.org/bugzilla/show_bug.cgi?id=63095 Christophe JAILLET changed: What|Removed |Added Attachment #36383|0 |1 is patch|| -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
[Bug 63256] mod_ssl segmentation fault after 2.4.29
https://bz.apache.org/bugzilla/show_bug.cgi?id=63256 --- Comment #20 from martin.l.schett...@leidos.com --- (In reply to Yann Ylavic from comment #18) > Created attachment 36488 [details] > mod_proxy to reset SSL dir config on connection reuse > > I think that the issue is the scope of sslconn->dc, when it's based off > r->per_dir_config it's also destroyed with the request, so we need to reset > it on connection reuse in mod_proxy. > > Does this patch work for you Martin? Yes, this patch fixes my issue. Thanks!! -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
[Bug 63256] mod_ssl segmentation fault after 2.4.29
https://bz.apache.org/bugzilla/show_bug.cgi?id=63256 --- Comment #19 from Yann Ylavic --- (In reply to Joe Orton from comment #17) > r being NULL in the callback looks significant possibly? The app data has > not been set up properly for the client-side SSL * in the proxy? Yes r is NULL in the proxy case (which r anyway?), but it should not really matter for the proxy case in ssl_callback_SSLVerify() because c->base_server == r->server (c == mod_proxy backend here). So provided sslconn->dc is right we should be good no? -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
[Bug 63256] mod_ssl segmentation fault after 2.4.29
https://bz.apache.org/bugzilla/show_bug.cgi?id=63256 --- Comment #18 from Yann Ylavic --- Created attachment 36488 --> https://bz.apache.org/bugzilla/attachment.cgi?id=36488=edit mod_proxy to reset SSL dir config on connection reuse I think that the issue is the scope of sslconn->dc, when it's based off r->per_dir_config it's also destroyed with the request, so we need to reset it on connection reuse in mod_proxy. Does this patch work for you Martin? -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
[Bug 63262] New: RewriteRule in section matches against file system path instead of URI path
https://bz.apache.org/bugzilla/show_bug.cgi?id=63262 Bug ID: 63262 Summary: RewriteRule in section matches against file system path instead of URI path Product: Apache httpd-2 Version: 2.4.38 Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: mod_rewrite Assignee: bugs@httpd.apache.org Reporter: klausru...@atmedia.net Target Milestone: --- When using RewriteRule in context, the pattern is matched against the file system path instead of the URI path: httpd.conf: RewriteEngine on LogLevel alert rewrite:trace8 RewriteRule ^(.*)$ http://example.localhost/?$1 [R=302,L] Request: http://example.com/test Expected response: Redirect to http://example.localhost/?/test Received response: Redirect to http://example.localhost/?/usr/www/htdocs/test Rewrite log: [Fri Mar 15 10:52:15.994467 2019] [mpm_winnt:notice] [pid 4976:tid 408] AH00455: Apache/2.4.38 (Win64) OpenSSL/1.0.2r configured -- resuming normal operations [Fri Mar 15 10:52:26.369060 2019] [rewrite:trace2] [pid 10744:tid 1128] mod_rewrite.c(483): [client 127.0.0.1:62192] 127.0.0.1 - - [localhost/sid#1d7798][rid#290ff40/initial] init rewrite engine with requested uri /test [Fri Mar 15 10:52:26.369060 2019] [rewrite:trace1] [pid 10744:tid 1128] mod_rewrite.c(483): [client 127.0.0.1:62192] 127.0.0.1 - - [localhost/sid#1d7798][rid#290ff40/initial] pass through /test [Fri Mar 15 10:52:26.377060 2019] [rewrite:trace3] [pid 10744:tid 1128] mod_rewrite.c(483): [client 127.0.0.1:62192] 127.0.0.1 - - [localhost/sid#1d7798][rid#290ff40/initial] [perdir *If/] applying pattern '^(.*)$' to uri '/usr/www/htdocs/test' [Fri Mar 15 10:52:26.377060 2019] [rewrite:trace2] [pid 10744:tid 1128] mod_rewrite.c(483): [client 127.0.0.1:62192] 127.0.0.1 - - [localhost/sid#1d7798][rid#290ff40/initial] [perdir *If/] rewrite '/usr/www/htdocs/test' -> 'http://example.localhost/?/usr/www/htdocs/test' -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
[Bug 63256] mod_ssl segmentation fault after 2.4.29
https://bz.apache.org/bugzilla/show_bug.cgi?id=63256 --- Comment #17 from Joe Orton --- r being NULL in the callback looks significant possibly? The app data has not been set up properly for the client-side SSL * in the proxy? -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
