Host header smee.io causing Jenkins webhook to fail

[dhanar10]

This issue starts happening to me today.

Based on my limited experiment, Jenkins BitBucket PPR webhook will fail with 404 error when it sees "host: smee.io" in request header. Removing the "host: smee.io" in request header works (I use curl to simulate this).

This is weird since smee-client has no changes for so long and the BitBucket PPR webhook plugin is last updated 3 months ago.

Does smee-client always include "host: smee.io" when invoking target webhook? If yes, then maybe an option to exlude "host: smee.io" when invoking target webhook would be nice.

[amarnath552]

Hi All,

I am trying to use Smee client to trigged the Job in Jenkins from git webhook. I created the new job in Jenkins and commit any change in the git, I am able to triggered the Job in Jenkins. When I tried to made any change in the git 2nd time, smee getting the response from git but job not triggered in the Jenkins. If removed the 1st build in the Jenkins and commit the changes in git it's working. smee --url https://smee.io/XXXXXxxxxxxx --target http://127.0.0.1:8080/github-webhook/ Finally if I removed all the old builds on the job,then only new build triggered.

Can any one please suggest or provide any solution on this issue.

[bmerry]

This is also causing problems when using an https target: one gets a certificate error like "Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: Host: smee.io. is not in the cert's altnames: DNS:xxx" where xxx is the target hostname.

[github-actions[bot]]

:tada: This issue has been resolved in version 2.0.3 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: