https://bz.apache.org/bugzilla/show_bug.cgi?id=45023
d...@ulupov.com changed:
What|Removed |Added
CC|d...@ulupov.com |
--
You are receiving this mail
https://bz.apache.org/bugzilla/show_bug.cgi?id=39727
d...@ulupov.com changed:
What|Removed |Added
CC|d...@ulupov.com |
--
You are receiving this mail
https://bz.apache.org/bugzilla/show_bug.cgi?id=53160
Christophe JAILLET changed:
What|Removed |Added
CC||al...@salesforce.com,
https://bz.apache.org/bugzilla/show_bug.cgi?id=59090
Rico Neubauer changed:
What|Removed |Added
CC||r.neuba...@seeburger.de
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=45023
Rainer Canavan changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|MOVED
https://bz.apache.org/bugzilla/show_bug.cgi?id=57876
--- Comment #4 from moh.riza ---
dont not issue
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail:
https://bz.apache.org/bugzilla/show_bug.cgi?id=57876
--- Comment #3 from moh.riza ---
dont not issue
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail:
https://bz.apache.org/bugzilla/show_bug.cgi?id=57876
--- Comment #2 from moh.riza ---
not google work windows
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail:
https://bz.apache.org/bugzilla/show_bug.cgi?id=45023
moh.riza changed:
What|Removed |Added
Resolution|--- |MOVED
Status|REOPENED
https://bz.apache.org/bugzilla/show_bug.cgi?id=59090
moh.riza changed:
What|Removed |Added
CC|r.neuba...@seeburger.de |
--
You are receiving this mail because:
https://bz.apache.org/bugzilla/show_bug.cgi?id=62318
--- Comment #8 from Jim Jagielski ---
Thx. Awaiting your check. I can confirm that the patch passes my tests which
recreated the original problem
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=53160
moh.riza changed:
What|Removed |Added
CC|al...@salesforce.com, |
|an...@treshna.com,
https://bz.apache.org/bugzilla/show_bug.cgi?id=61499
--- Comment #5 from Jim Jagielski ---
Yes, it does not do the double-set for HTTP so this is likely fluff left over
from the rework around 2.4.27.
Thx for the patch
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61499
--- Comment #4 from Dominik Stillhard
---
the line i was talking about:
https://github.com/apache/httpd/blob/5bd8f20a5063f47e93fe148032ec8ffa5d04a12e/modules/proxy/mod_proxy_hcheck.c#L615
;)
--
You are receiving this mail because:
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=61499
--- Comment #3 from Dominik Stillhard
---
I tested this in version 2.3.34 and the bug still exists.
The problem is, that compare to http checks, in the function
ap_proxy_connect_backend (proxy_util.c) the backend_addr is NULL.
Thats why
https://bz.apache.org/bugzilla/show_bug.cgi?id=61499
--- Comment #2 from Dominik Stillhard
---
Created attachment 36143
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36143=edit
patch removing the line, based on trunk
--
You are receiving this mail because:
You are the assignee for
https://bz.apache.org/bugzilla/show_bug.cgi?id=62697
Joe Orton changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=62697
--- Comment #3 from Joe Orton ---
Good catch, thanks for the report and patch. I think it would be slightly
better to do the READY=1 in a post_config hook actually outside of the monitor
hook. At this point the serer is listening TCP ports
18 matches
Mail list logo