-
Suggestion
-
Resolution: Timed out
-
None
-
RHEL, Apache, Lighttpd
-
0
-
1
-
One common method of putting a proxy-server in front of a Java appserver is to use mod_proxy. However, when using mod_proxy the connecting IP address is proxying host (often 127.0.0.1), which breaks triggers as the connecting host won't match the repository host. Note that this will also apply where other forms or proxies (load-balancers, client caching proxies) are in place.
One option is to inspect the headers for the 'X-Forwarded-For:' header, which contains the IP of the original connecting host. The longer term (probably correct) option is to use HTTP-basic auth instead of IP filtering.
[BAM-1172] Bamboo doesn't recognise repository address when fronted by a proxy server
Resolution | New: Timed out [ 10 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Labels | Original: bamboo-bugfix-kanban-candidate | New: bamboo-bugfix-kanban-candidate bamboo-bugs-grooming |
Workflow | Original: JAC Suggestion Workflow [ 3015950 ] | New: JAC Suggestion Workflow 3 [ 3606750 ] |
Labels | New: bamboo-bugfix-kanban-candidate |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2702531 ] | New: JAC Suggestion Workflow [ 3015950 ] |
UIS | New: 0 |
Support reference count | New: 1 |
Backlog Order (Obsolete) | Original: 4820000000 | |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1420322 ] | New: Confluence Workflow - Public Facing v4 [ 2702531 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 615859 ] | New: Bamboo Workflow 2016 v1 [ 1420322 ] |