We are trying to use “Trigger builds remotely” (webhooks) with Bitbucket on our Jenkins 2.462.1 installation, but something is funky:
When I use the hook URL on my machine, I get the pipeline to trigger.
But when Bitbucket calls it, it shows it got a 403 response back.
I’m trying to log all incoming requests to figure out if our firewall is mangling the URL ('cause it has some weird rules, don’t ask me), but I can’t really find what I need to enable.
I tried enabling “Jetty” in the custom log options, and it does show the URL, but only a part of it, followed by a bunch of NUL indicators, which is not helpful.
Is there a way to log the incoming requests, so I can check if the URL is getting destroyed somewhere?