-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
6.3.8, 6.4, 6.4.2, 6.4.4, 6.4.5, 6.4.8, 6.4.9, 6.4.11, 6.4.12, 6.4.13, 7.0.5, 7.1.0, 7.1.7, 7.2.1, 7.3.0, 7.2.3, 7.2.9, 7.3.6, 7.3.8, 7.7.1, 7.5.5
-
6.03
-
57
-
Severity 2 - Major
-
216
-
-
Atlassian Update – 22 March 2018
Hello everyone,
Pleased to announce that fix has been committed and now awaits a release. We are planning to release 7.8.2 and 7.9.0 versions in few weeks.
Fix would be available for Jira 7.6.5 too, which is current Jira Enterprise release, yet the release date is unknown as of today.Details of the fix
As it was mentioned - the issue was isolated in an internal component AHTTP-36.
Upgrading the component inside the product resolves the issue. Fix has been tested Jira versions 7.6.5, 7.7.3, 7.8.2, 7.9.0.Upgrading
While it is possible to upgrade a component out of band - Atlassian recommends upgrading to nearest bugfix release to get the fix.
Out-of-band component upgrades may lead to support team reject support cases until Jira code and plugins is in original versions. Also out-of-band deployments also may have a critical impact on instance stability and performance because of JRASERVER-64908.In any case - I'm attaching the mentioned version of the component that contain the fix - atlassian-httpclient-plugin-1.0.1.jar, which may be upgraded if the mentioned risks are tolerable.
Configuration
Please mind that there are different proxy configuration options available for http and https (http.proxyHost, https.proxyHost). All the details are available in https://confluence.atlassian.com/jirakb/how-to-configure-an-outbound-http-and-https-proxy-for-jira-applications-247857187.html
Wish you a smooth upgrades.
Cheers,
Ignat Alexeyenko
Jira BugmasterAtlassian Update – 22 March 2018 Hello everyone, Pleased to announce that fix has been committed and now awaits a release. We are planning to release 7.8.2 and 7.9.0 versions in few weeks. Fix would be available for Jira 7.6.5 too, which is current Jira Enterprise release, yet the release date is unknown as of today. Details of the fix As it was mentioned - the issue was isolated in an internal component AHTTP-36 . Upgrading the component inside the product resolves the issue. Fix has been tested Jira versions 7.6.5, 7.7.3, 7.8.2, 7.9.0. Upgrading While it is possible to upgrade a component out of band - Atlassian recommends upgrading to nearest bugfix release to get the fix. Out-of-band component upgrades may lead to support team reject support cases until Jira code and plugins is in original versions. Also out-of-band deployments also may have a critical impact on instance stability and performance because of JRASERVER-64908 . In any case - I'm attaching the mentioned version of the component that contain the fix - atlassian-httpclient-plugin-1.0.1.jar, which may be upgraded if the mentioned risks are tolerable. Configuration Please mind that there are different proxy configuration options available for http and https (http.proxyHost, https.proxyHost). All the details are available in https://confluence.atlassian.com/jirakb/how-to-configure-an-outbound-http-and-https-proxy-for-jira-applications-247857187.html Wish you a smooth upgrades. Cheers, Ignat Alexeyenko Jira Bugmaster
Steps to reproduce the problem
- Install a Charles Proxy
- Create a HTTP proxy settings via Charles - see http-proxy.png
- Configure the parameters below to JVM argument via $JIRA_INSTALL/bin/setenv file:
-Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=8888 -Dhttp.nonProxyHosts=requestb.in
- Save it and start JIRA.
- Configure a webhook to http://requestb.in/ for example like this test-webhook-642.png
- Create a new issue to fire a webhook.
- The http://requestb.in URL is showing in the Charles traffic (which mean -Dhttp.nonProxyHosts is not working).
Expected Result
The -Dhttp.nonProxyHosts is respected and the traffic is not directed to the proxy. The Request Bin URL shouldn't be showed in the traffic if the -Dhttp.nonProxyHosts is working.
Actual Result
The WebHook goes through the proxy.
From the logs :
2016-01-19 13:25:00,973 httpclient-callbacks:thread-23 WARN anonymous [atlassian.webhooks.plugin.PublishTaskFactoryImpl$PublishTaskImpl] Client error - 400 when posting to web hook at 'http://requestb.in/xxxxx'
Additional Information
- Tested on 6.4.2 and 6.4.3
- The problem is not occurring in JIRA 6.3.15, thus this is a regression.
Workaround
See "Upgrading" section from Current status
- is duplicated by
-
JRASERVER-43088
Webhook doesn't respect -Dhttp.nonProxyHosts
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Gathering Impact
-
-
RAID-835 You do not have permission to view this issue
- is blocked by
-
PSR-58 Loading...
- mentioned in
-
-
-
-
-
-
- was cloned as
-
Webhooks failing to bypass proxy when receiving URL is configured as a nonProxyHost in JVM configuration
-
-
Resolution: Fixed
-
Medium
-
6.3.8, 6.4, 6.4.2, 6.4.4, 6.4.5, 6.4.8, 6.4.9, 6.4.11, 6.4.12, 6.4.13, 7.0.5, 7.1.0, 7.1.7, 7.2.1, 7.3.0, 7.2.3, 7.2.9, 7.3.6, 7.3.8, 7.7.1, 7.5.5
-
6.03
-
57
-
Severity 2 - Major
-
216
-
-
Atlassian Update – 22 March 2018
Hello everyone,
Pleased to announce that fix has been committed and now awaits a release. We are planning to release 7.8.2 and 7.9.0 versions in few weeks.
Fix would be available for Jira 7.6.5 too, which is current Jira Enterprise release, yet the release date is unknown as of today.Details of the fix
As it was mentioned - the issue was isolated in an internal component AHTTP-36.
Upgrading the component inside the product resolves the issue. Fix has been tested Jira versions 7.6.5, 7.7.3, 7.8.2, 7.9.0.Upgrading
While it is possible to upgrade a component out of band - Atlassian recommends upgrading to nearest bugfix release to get the fix. Out-of-band component upgrades may lead to support team reject support cases until Jira code and plugins is in original versions. Also out-of-band deployments also may have a critical impact on instance stability and performance because of JRASERVER-64908.In any case - I'm attaching the mentioned version of the component that contain the fix - atlassian-httpclient-plugin-1.0.1.jar, which may be upgraded if the mentioned risks are tolerable.
Configuration
Please mind that there are different proxy configuration options available for http and https (http.proxyHost, https.proxyHost). All the details are available in https://confluence.atlassian.com/jirakb/how-to-configure-an-outbound-http-and-https-proxy-for-jira-applications-247857187.html
Wish you a smooth upgrades.
Cheers,
Ignat Alexeyenko
Jira BugmasterAtlassian Update – 22 March 2018 Hello everyone, Pleased to announce that fix has been committed and now awaits a release. We are planning to release 7.8.2 and 7.9.0 versions in few weeks. Fix would be available for Jira 7.6.5 too, which is current Jira Enterprise release, yet the release date is unknown as of today. Details of the fix As it was mentioned - the issue was isolated in an internal component AHTTP-36 . Upgrading the component inside the product resolves the issue. Fix has been tested Jira versions 7.6.5, 7.7.3, 7.8.2, 7.9.0. Upgrading While it is possible to upgrade a component out of band - Atlassian recommends upgrading to nearest bugfix release to get the fix. Out-of-band component upgrades may lead to support team reject support cases until Jira code and plugins is in original versions. Also out-of-band deployments also may have a critical impact on instance stability and performance because of JRASERVER-64908 . In any case - I'm attaching the mentioned version of the component that contain the fix - atlassian-httpclient-plugin-1.0.1.jar, which may be upgraded if the mentioned risks are tolerable. Configuration Please mind that there are different proxy configuration options available for http and https (http.proxyHost, https.proxyHost). All the details are available in https://confluence.atlassian.com/jirakb/how-to-configure-an-outbound-http-and-https-proxy-for-jira-applications-247857187.html Wish you a smooth upgrades. Cheers, Ignat Alexeyenko Jira Bugmaster
Steps to reproduce the problem
- Install a Charles Proxy
- Create a HTTP proxy settings via Charles - see http-proxy.png
- Configure the parameters below to JVM argument via $JIRA_INSTALL/bin/setenv file:
-Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=8888 -Dhttp.nonProxyHosts=requestb.in
- Save it and start JIRA.
- Configure a webhook to http://requestb.in/ for example like this test-webhook-642.png
- Create a new issue to fire a webhook.
- The http://requestb.in URL is showing in the Charles traffic (which mean -Dhttp.nonProxyHosts is not working).
Expected Result
The -Dhttp.nonProxyHosts is respected and the traffic is not directed to the proxy. The Request Bin URL shouldn't be showed in the traffic if the -Dhttp.nonProxyHosts is working.
Actual Result
The WebHook goes through the proxy.
From the logs :
2016-01-19 13:25:00,973 httpclient-callbacks:thread-23 WARN anonymous [atlassian.webhooks.plugin.PublishTaskFactoryImpl$PublishTaskImpl] Client error - 400 when posting to web hook at 'http://requestb.in/xxxxx'
Additional Information
- Tested on 6.4.2 and 6.4.3
- The problem is not occurring in JIRA 6.3.15, thus this is a regression.
Workaround
See "Upgrading" section from Current status
- is duplicated by
-
JRASERVER-43088
Webhook doesn't respect -Dhttp.nonProxyHosts
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Gathering Impact
-
-
- is blocked by
-
- mentioned in
-
-
-
-
-
-
- was cloned as
-
-
Ignat (Inactive)
-
- Votes:
-
131 Vote for this issue
- Watchers:
-
125 Start watching this issue
- Created:
- Updated:
- Resolved: