Pathod: A pathological HTTP daemon for testing and torturing client software
1–10 of 15 posts
Re: Pathod: A pathological HTTP daemon for testing and torturing client software
#2What's the practical usage scenario for this? Would it be only used by http client library developers, or is there a broader audience?
Re: Pathod: A pathological HTTP daemon for testing and torturing client software
#3Drat - this story is just a tad premature. A brand new release of pathod will be out next week, including a publicly accessible pathod instance, pathoc (pathod's evil client-side equivalent), and a huge range of other improvements and bugfixes.
Re: Pathod: A pathological HTTP daemon for testing and torturing client software
#4What's the practical usage scenario for this? Would it be only used by http client library developers, or is there a broader audience?
I started work on pathod to improve the testing of mitmproxy (http://mitmproxy.org). It's since become a very capable Swiss army knife with many creative uses. I now routinely use it in pen tests (it's great for exploit delivery), and pathoc has become quite a capable tool for simple fuzzing and stress testing. I'm working on the next release docs as we speak, and I'll try to document a range of different use cases there.
Re: Pathod: A pathological HTTP daemon for testing and torturing client software
#5What's the practical usage scenario for this? Would it be only used by http client library developers, or is there a broader audience?
Or you could hand examples of your favorite rogue web bot a whole pile of confusing chunder.
Re: Pathod: A pathological HTTP daemon for testing and torturing client software
#6This is a similar tool as http://httpbin.org/ which was written by Kenneth Reitz to test python request http://python-requests.org/. I like that this is written in tornado thanks for sharing.
Re: Pathod: A pathological HTTP daemon for testing and torturing client software
#7bane is a similar tool that pathod-interested users might be interested in.
https://github.com/danielwellman/bane
From the readme: "If you are building an application, you may depend on third-party servers or web services for your data. Most of the time these services are reliable, but at some point they will behave in an unusual manner - such as connecting but never respond, sending data very slowly, or sending an unexpected response. To ensure your application survives these scenarios, you should test your application against these bad behaviors. Bane helps you recreate these scenarios by standing in for your third-party servers and responding in several nefarious ways."
Re: Pathod: A pathological HTTP daemon for testing and torturing client software
#8This is a similar tool as http://httpbin.org/ which was written by Kenneth Reitz to test python request http://python-requests.org/ . I like that this is written in tornado thanks for sharing.
One difference is that pathod (and pathoc, the client-side equivalent) works hard to make it possible to violate the HTTP protocol specs at will, in pretty much arbitrary ways. The next version of pathod also moves away from Tornado to let it take more direct control of comms.
Re: Pathod: A pathological HTTP daemon for testing and torturing client software
#9Drat - this story is just a tad premature. A brand new release of pathod will be out next week, including a publicly accessible pathod instance, pathoc (pathod's evil client-side equivalent), and a huge range of other improvements and bugfixes.
apols
Re: Pathod: A pathological HTTP daemon for testing and torturing client software
#10Drat - this story is just a tad premature. A brand new release of pathod will be out next week, including a publicly accessible pathod instance, pathoc (pathod's evil client-side equivalent), and a huge range of other improvements and bugfixes.
apols
No, thanks for posting! Just upvote again when you see the release notice next week. :)