I am getting the following error from my chrome while testing it using my React App from http://localhost:8080: Failed to load https://webhook.site/a0dc4f6a-7044-442a-89db-e14ec228da4d: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:8080' is therefore not allowed access.. From my understanding, by default Chrome sends an OPTION request to the domain if it's different than current. I am suspecting, the app doesn't accept OPTIONS requests. Perhaps this package might help for Laravel: https://github.com/barryvdh/laravel-cors.

Hi, I'm using webhook.site container, I added my pusher credentials at .env file. When I'm receiving webhooks, the webhook page hasn't been notified, is there something to do in the pusher side? I'm receiving webhook messages on pusher side and I need to refresh my webhook page manually to see the messages

I'm experiencing frequent internal server errors just trying to create a new testing url - this error changes sometimes to curl: (52) Empty reply from server and curl: (35) Unknown SSL protocol error in connection to webhook.site:443

Adds support for syntax highlighting of XML and JSON files (#5)

• Just JS/JSON and XML support enabled for now (to optimise JS size)
• Does a shallow copy of the currentRequest (so that when changes are made the original is not overriden)
• Enable formatting in the setCurrentRequest method
• Adds XML pretty printing/formatting as well

Fixes #5 Fixes #60

There already exists an option to forward requests to an arbritrary address, I was wondering if we could get the functionality to redirect a request to an arbritrary URL?

Happens on https://webhook.site/#!/f4401c90-snipped.

1. [ ] Click "Next page" - get 401 Unauthorized in the console.
2. [ ] Click "Next page" - nothing happens, no user feedback - UI error handling problem.

Regarding the latter, this happens very often in single page applications. It's easy to forget to handle an error. There's a need for global error handler that will display an error if any request fails. Below is how it got done at my company.

And the implemented design:

Here's something for JQuery: https://stackoverflow.com/questions/17989961/jquery-catch-any-ajax-error. I'm sure an equivalent mechanism exists for whatever webhook.site uses.

Before Thanksgiving I bought a Premium version, created a new webhook site starting with f4401c90, enabled password protection on it, and tested it actually worked - both webhook at https://webhook.site/f4401c90-snipped, as well as the UI at https://webhook.site/#!/f4401c90-snipped.

My intent was to leave this running for the weekend, and see all the requests today. I checked today and it no longer works. https://webhook.site/#!/f4401c90-4940-snipped no longer prompts for password. And the page seems borked when I visit it (the unique URL is incorrect).

However, the webhook itself at https://webhook.site/f4401c90-snipped does function, as it returns the JSON content I configured it to return:

{
  "autoConfirm": false,
  "attributes": {
    "nowakertest": "test"
  }
}

Can you please look into the problem and fix it so that I can access my webhook request history at https://webhook.site/#!/f4401c90-snipped? Thanks!

I upgraded and now I can't see all my requests on the left like I could in the regular version. I see you have links now to navigate thru entries but the Next-> link is not working so I have to go all the way back to end and start over moving back thru.

Please give option to list all on left like unpaid version.

for some reason, when sending a GET with some queries, it does not show the query.

is there any in-container configuration i need to apply to see the queries?

Hello,

It seems that new line characters are stripped away during request body processing. E.g.:

printf "%s\n%s\n%s\n%s\n" a b c d | curl -H 'Content-Type: text/plain' -v -d@- https://webhook.site/38e09213-6ad6-42b0-8cb5-890939757c31

results into both "raw content" page and html preview at permalink not showing any new lines. Adding "\r" to the mix does not seem to help the case.

Thanks!

The ability to secure webhook data is important.

When I've been developing against webhooks, sometimes it's hard to get dummy or fake data, instead, the webhook is sent with real/client/private information. The ability to secure either the entire webhook site or a single token behind a login such as G-Suite login would be ideal.

I can see you have a paid patreon feature "Password Protection".

Ideally, I'd like to self-host this, securing by requiring G-Suite login to view any webhooks received.

I have Zammad in a docker-compose-stack url using its own docker network, the main zammad application is exposed on the docker-host on port 9015 and is accessed via HAproxy.

From Zammad I try to "contact" your application running in another stack, exposed on port 8084.

IP of docker-host is 192.168.97.160, so a URL of your app is

http://192.168.97.160:8084/0ad520c0-be1e-4f23-b488-bee8f3db1933

I create a webhook in zammad using that URL, plus a trigger, but I don't see anything happening in the "webhook.site" GUI.

I assume that should work, but don't know how to proceed. Any hints?

For example I tried to join the tester app to the zammad docker network and use the container IP as in

http://172.22.0.4:80/0ad520c0-be1e-4f23-b488-bee8f3db1933

Still nothing.

In the zammad logs I see the trigger activated and the hook called.

And yes, I asked the zammad folks as well forum

thanks for any hints

Sometimes, in some slow VPS, when trying to start with docker compose, the webapp instance loads before the redis which causes a connection error.

i've been only been able to reproduce this in a basic DigitallOcean VPS. It doesn't happen all the time tho.

This PR just add a depends_on to make this loading order explicit

It would have been great to have customizable domains like this: {guid}.webhook.site, with webhooks created inside this domain looking like this {guid}.webhook.site/{path}. That way you can create a domain for every service you're trying to mock and then create mocked paths inside each domain.

After submitting a simple XML request to Webhook cloud, the XML pretty print is not applied.

Request:

curl --location --request GET 'https://webhook.site/[guid]' \
--header 'Content-Type: text/xml' \
--data-raw '<note>
<to>Tove</to>
<from>Jani</from>
<heading>Reminder</heading>
<body>Don'\''t forget me this weekend!</body>
</note>'

I noticed this originally because SOAP requests are not formatted.

Hi all,

I succeed in starting locally in my wsl, with docker-compose, webhook.site.

But when I try to deploy into a K8s service (OCP), the webhook crashloop at start with this error : s6-mkdir: warning: unable to mkdir /var/run/s6: Permission denied

I tried to rebuild the image, removing the user root at the end of the docker file, but it's not enough to make it start in a k8s service where process as user root are not allowed.

Can you help me make it work as non root user ?