How do you generate that unique endpoint? Do you have some worker that generates https config? Whats your magic ?
This StackOverflow post explains how it can be done with Nginx: https://stackoverflow.com/questions/12950572/nginx-wildcard-...
Show HN: Endpoints.dev – Pastebin for HTTP Requests
21–30 of 52 posts
Re: Show HN: Endpoints.dev – Pastebin for HTTP Requests
#22Earlier quoted context omitted.
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.
If I knew somebody else's unique subdomain, I could set my browser cookie on my local computer to that value and it seems to just load the other subdomain just fine. I tested this with 2 different browser on my same laptop. Maybe it won't work if the other person is on another computer? I could also just set the subdomain to anything I like (by setting the cookie value) and it still works just fine. Ah no, I can stil…
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
Re: Show HN: Endpoints.dev – Pastebin for HTTP Requests
#23Feature request: give me a URL I can bookmark or share with team-mates for the HTTP inspector bit. It looks at the moment like I get a random URL to send requests to but I have to use the same browser to ensure that the endpoints.dev homepage knows who I am so it can show me the traffic.
Re: Show HN: Endpoints.dev – Pastebin for HTTP Requests
#24Feature request: give me a URL I can bookmark or share with team-mates for the HTTP inspector bit. It looks at the moment like I get a random URL to send requests to but I have to use the same browser to ensure that the endpoints.dev homepage knows who I am so it can show me the traffic.
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.
Re: Show HN: Endpoints.dev – Pastebin for HTTP Requests
#25Earlier quoted context omitted.
oh. you don't have live-updating. Sorry it works then.
Live updating should work - I'll investigate if there's any issues with the websocket api :)
Same, live updating didn't work but a page refresh did. I don't know much about websockets, but FWIW this request is still pending:
Request URL: wss://ws.endpoints.dev/?token=redacted
Request Method: GET
Status Code: 101 Switching ProtocolsRe: Show HN: Endpoints.dev – Pastebin for HTTP Requests
#26Earlier quoted context omitted.
oh. you don't have live-updating. Sorry it works then.
Live updating should work - I'll investigate if there's any issues with the websocket api :)
Fixing the real time update would be my only immediate feedback. Outside of that, this is a pretty nice app
Re: Show HN: Endpoints.dev – Pastebin for HTTP Requests
#27Earlier quoted context omitted.
oh. you don't have live-updating. Sorry it works then.
Live updating should work - I'll investigate if there's any issues with the websocket api :)
Live updating also not working for me. I do have uMatrix installed but I whitelisted your whole site for each column.
Re: Show HN: Endpoints.dev – Pastebin for HTTP Requests
#28Show me your pretty requests everybody:
https://2f5799dcfb.endpoints.dev
# Update
Interesting:
- Lots of IPV6 requests coming from HN.
- What is the "dnt" header most requests carry?
Re: Show HN: Endpoints.dev – Pastebin for HTTP Requests
#29Earlier quoted context omitted.
Very cool. You can also use osapy.com to inspect 3rd party API requests. Or even combine Osapy with endpoints.dev. I wrote a blogpost how to do that for retool. In which direction do you want to develop the website?
Actually - just tried your website and it doesn't work for me. I tried curl -H "Content-Type: application/json" -d '{"message":"hello world"}' https://8ef216dd46.endpoints.dev and nothing happened. Maybe check your logs.
Are you running behind a load balancer on AWS? You might have to increase the idle connection timeout from the default (60 seconds). I use the max 4000s on hopps.io. Sending keep alive's to prevent the socket connection from closing also helps. Not sure if that's your issue, but worth looking into...
Re: Show HN: Endpoints.dev – Pastebin for HTTP Requests
#30Show me your pretty requests everybody: https://2f5799dcfb.endpoints.dev # Update Interesting: - Lots of IPV6 requests coming from HN. - What is the "dnt" header most requests carry?
It is the "Do Not Track" header[1], which indicates that the user doesn't want to be tracked.
[1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/DN...