Bitbucket Data Center does not send the web-hook to the Bitbucket Mirror when proxy bypass is enabled.

Summary

Bitbucket Data Center does not send the web-hook to the Bitbucket Mirror when proxy bypass is enabled. This causes the Bitbucket Mirror to be updated every 15 min not instantaneously. Once this setting is cleared, Bitbucket Data Center sends the web hook to the Bitbucket Mirror. There is a INFO log generated by c.a.w.i.p.DefaultWebhookDispatcher on Bitbucket Data Center.

-Dhttp.nonProxyHosts=""*.<your domain>.com|localhost""

Steps to Reproduce

1. Set up Bitbucket Data Center on a network that only needs a proxy to access the internet. Configure to use -Dhttp.nonProxyHosts= for the network.
2. Confirm Bitbucket Data Center has access to the Marketplace.
3. Set up a Bitbucket Mirror.
4. Push a commit to a repository that the Bitbucket Mirror is mirroring.
5. The Bitbucket Mirror will in ~ 15 min pull the change from Bitbucket Data Center.
6. Remove the proxy setting from the Bitbucket Data Center instance and restart.
7. Repeat push. Note that the Access Logs on the Bitbucket Mirror show the incoming web hook and the repository is synced immediately.

Expected Results

Bitbucket Data Center will make an outbound web hook connection to the Bitbucket Mirror. This will be logged in the Bitbucket Mirror access logs as an incoming connection.

Actual Results

c.a.w.i.p.DefaultWebhookDispatcher will log the following:

111-11-11 11:11:11,111 INFO  [ForkJoinPool.commonPool-worker-*]  c.a.w.i.p.DefaultWebhookDispatcher Webhook invocation [...] 
	failed with an error

The Bitbucket Mirror will revert to the 15 pull timer to pull updates.

Workaround

Remove proxy settings from Bitbucket Data Center.