I wrote a similar tool while debugging a web scraper for my current dayjob employer, but it was buried inside of our application rather than standalone.
(Also, it was PHP, which a lot of people hate.)
httpdiff – diff responses to two HTTP/HTTPS requests
11–20 of 41 posts
Re: httpdiff – diff responses to two HTTP/HTTPS requests
#12Why not just write this as a bash one-liner? function httpdiff { diff
Try
httpdiff https://www.google.com http://www.google.com/Re: httpdiff – diff responses to two HTTP/HTTPS requests
#13Awesome tool! Our Traffic Inspector also has this feature for requests captured through our API debugging proxy: https://www.runscope.com/docs/comparisons
Re: httpdiff – diff responses to two HTTP/HTTPS requests
#14The Unix way: diff &1) &1) As a shell function: httpdiff () { diff &1) &1) } httpdiff https://news.ycombinator.com/ https://news.ycombinator.com/
Which works well for that one example. But not others. diff &1) &1) On my machine that produces 33k of output. I like one liners and using the shell, but this tool was built not for fun because I was debugging things that were painful.
That's nothing a couple "1> /dev/null"'s can't solve (or redirect to a temporary file then "diff -q"). But yeah, yours is a bit nicer.
Re: httpdiff – diff responses to two HTTP/HTTPS requests
#15Perfect use case for Go.
Re: httpdiff – diff responses to two HTTP/HTTPS requests
#16Very cool! I'm a bit of a newb though - how do I install this?
1. You need Go 2a. Type 'make'. It will build the binary and place it in bin/ 2b. Use the go tool chain directly to build. Does the same thing as 2a.
why the makefile and src directory? Why not put the source in the root directory, so that go get github.com/jgrahamc/httpdiff would just work? The makefile doesn't even do anything useful, and just makes it so that poor windows folks can't build your code for no good reason.
Re: httpdiff – diff responses to two HTTP/HTTPS requests
#17Earlier quoted context omitted.
1. You need Go 2a. Type 'make'. It will build the binary and place it in bin/ 2b. Use the go tool chain directly to build. Does the same thing as 2a.
why the makefile and src directory? Why not put the source in the root directory, so that go get github.com/jgrahamc/httpdiff would just work? The makefile doesn't even do anything useful, and just makes it so that poor windows folks can't build your code for no good reason.
Yes, you have to do the archaic `go get github.com/jgrahamc/httpdiff/src/httpdiff`. Truly a travesty. While the makefile allows you to avoid the whole GOPATH nonsense, which gets a plus from me.
Re: httpdiff – diff responses to two HTTP/HTTPS requests
#18Earlier quoted context omitted.
1. You need Go 2a. Type 'make'. It will build the binary and place it in bin/ 2b. Use the go tool chain directly to build. Does the same thing as 2a.
why the makefile and src directory? Why not put the source in the root directory, so that go get github.com/jgrahamc/httpdiff would just work? The makefile doesn't even do anything useful, and just makes it so that poor windows folks can't build your code for no good reason.
Because... bad habits from larger projects.
Re: httpdiff – diff responses to two HTTP/HTTPS requests
#19Getting x509 issues. Output is below:
$ httpdiff https://www.google.com http://www.google.com
Doing GET: https://www.google.com http://www.google.com
Error doing GET https://www.google.com: Get https://www.google.com: x509: certificate signed by unknown authority
I'm sitting behind a pretty heavy proxy though; could be that. That or OS X(10.9.5) certificate store issue maybe?
Re: httpdiff – diff responses to two HTTP/HTTPS requests
#20is there any reason to use md5? (apart from backward compatibility etc.)