You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i've a somewhat weird use case perhaps. I'm exposing an ipv6 service using a ddns services. Now since GitHub does not allow to enter ipv6 adresses for payload urls I did the following:
on a public cloud vps i've installed webhook using ipv4
added this target as new payload url in my github webhooks config
configured a command which executes a shell script with a curl replicating the github request and forwarding it to my ipv6 service
my service now can handle the webhook
while this is total overkill and a simple nginx reverse proxy config could have already solved my trouble it was nevertheless a fun experience to learn more about this app.
so much for the use cases, now the 2 issues I have.
I'm not sure how to exactly mimic the request delegation with curl. do you have an example or is there perhaps already a built in reverse proxy feature? and secondly how can I make the command fail (non 200) if the curl request results in an error?
The text was updated successfully, but these errors were encountered:
zewa666
changed the title
forward request to another instance
forward request to another api endpoint
Jan 1, 2022
hey there
i've a somewhat weird use case perhaps. I'm exposing an ipv6 service using a ddns services. Now since GitHub does not allow to enter ipv6 adresses for payload urls I did the following:
while this is total overkill and a simple nginx reverse proxy config could have already solved my trouble it was nevertheless a fun experience to learn more about this app.
so much for the use cases, now the 2 issues I have.
I'm not sure how to exactly mimic the request delegation with curl. do you have an example or is there perhaps already a built in reverse proxy feature? and secondly how can I make the command fail (non 200) if the curl request results in an error?
The text was updated successfully, but these errors were encountered: