twitter-archive / diffy

Find potential bugs in your services with Diffy
https://twitter.com/diffyproject
Apache License 2.0
3.83k stars 368 forks source link

Encounter a problem while setting up diffy tutorial... #20

Closed ianking closed 4 years ago

ianking commented 8 years ago

hi,

i encountered a problem while setting up the tutorial... and that is probably due to the header "Host" sent by the diffy.

the tutorial has 3 urls,

  1. http://http-candidate.herokuapp.com
  2. http://http-primary.herokuapp.com
  3. http://http-secondary.herokuapp.com

and here is the traffic from diffy,

  1. http://http-candidate.herokuapp.com 174.129.192.57 GET / HTTP/1.1 Host: localhost:8990 User-Agent: curl/7.43.0 Accept: / Canonical-Resource: Html
  2. http://http-primary.herokuapp.com 174.129.192.57 GET / HTTP/1.1 Host: localhost:8990 User-Agent: curl/7.43.0 Accept: / Canonical-Resource: Html
  3. http://http-secondary.herokuapp.com 54.83.197.202 GET / HTTP/1.1 Host: localhost:8990 User-Agent: curl/7.43.0 Accept: / Canonical-Resource: Html

it seems 1. and 2. are in the same instance, and depend on "Host" to determine the response, but the header "Host" from diffy is "localhost:8990", so the services always return 404...

removing the filter of Host from server or using the diffy proxy to change Host to http-xxxxx.herokuapp.com (the value from example.sh) may help.

2015-09-22 2 24 40

2015-09-22 2 24 57

scottclem commented 8 years ago

I am also experiencing this issue.

harrypotterismyname commented 8 years ago

I'm also experiencing this issue, look like diffy resolve hostname into IP before sending the request

jamesweb1 commented 8 years ago

How do you see the traffic from diffy? I also get the same response(404) as yours... How to solve this issue?