bozly

Wildcard DNS records (i.e. `*.example.com`) are your friend in situations like this :)

Found the bug! Live updating should be working now

I understand the frustration of too many logins :)

If I do end up adding user accounts, it would only be to add extra functionality (persistent URLs etc) - the existing functionality + potential perma-link feature would all remain available without an account.

The header details can be expanded by clicking the ">" arrow to the left of the "[{...},{...},etc]"

I think this could be a bit more intuitive though, thanks for the feedback!

they are auto generated by `styled-components` - a great option for "css in js" in the React ecosystem

Great idea, having a perma-link as an alternative to the browser cookie would be very nice - I'll add this to my list :)

I'm currently working on user accounts, which will eliminate the need to use the same browser.

Oh boy, that's an embarrassing bug!

Found the issue, and I'm working on fix now

Edit: bug squashed - this should no longer be an issue

Live updating should work - I'll investigate if there's any issues with the websocket api :)

hmm - I can see a few requests have been received & stored for that endpoint.. It could be that your client killed the connection to the websocket api - does refreshing the page show the requests?

Thanks, simplicity is definitely what I am aiming for!

Making this an OSS project is the direction I plan to take - just need to tidy up the code a bit before making it public :)

The current implementation is serverless on AWS though, and most of the "complexitly" is in the infrastructure, so as convenient as they are, I don't think I'll aim to dockerize it.

This was definitely a concern... Each unique subdomain is checked for collision before being assigned, so no two users will receive the same endpoint. Additionally, it is assigned with a jwt, so even if someone was to brute force an endpoint that has been assigned to someone else, they would not be authorized to see the request data.

yep, that's exactly it :) - I'm using an ALB on AWS to manage the incoming requests

Looks like requestbin will only keep 20 requests for 48 hours. Currently, endpoints.dev will store an unlimited number of requests for 30 days. The plan is to add user login, and lift the 30 day limit for authenticated users.

Thanks! webhook.site also looks great, I love their inclusion of an email address... I might take some inspiration from them in my next iteration ;)

I've just released endpoints.dev - Use it to get a unique, private url that will store & display all http requests made to it. Use your unique URL with 3rd party tools to see what requests they are making, without needing to spin up a webserver. Or, use it for experimenting with XXS, phone-home, and other http based pen-testing.