31–40 of 52 posts
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.
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.
Just out of curiosity, what's with all the freaky class names? Like class="sc-jTzLTM ipDHfO", class="sc-jzJRlG hdyVuB" etc.
Feature 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.
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.
Just out of curiosity, what's with all the freaky class names? Like class="sc-jTzLTM ipDHfO", class="sc-jzJRlG hdyVuB" etc.
Right now the Headers column is essentially useless because the json renderer doesn't seem to want to display beyond one level of depth so you just see "[{...},{...},etc]". Can you make this more usable? Maybe add some kind of expansion ui where it will pretty print the headers in multiple lines?
I think this could be a bit more intuitive though, thanks for the feedback!
Show 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...
Earlier quoted context omitted.
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.
Please do not require to login! The sharing via a second unique url would be great for teams and I could use it right away. If I have to convince all my colleges to login that would kill it for me :/
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.
Earlier quoted context omitted.
Any advantages over http://requestbin.net/ ?
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.