Re: Why doesn't Firebug show ALL HTTP headers?

[Sebastian Zartner]

Do you have a URL, which has this problem, so we can reproduce this?

Sebastian

On Tuesday, March 19, 2013 7:42:34 AM UTC-5, Thomas Augustin wrote:

Hello everyone,

I am wondering, why Firebug doesn't show e.g. the X_Forwarded_For HTTP header, as I'd expect it from a developer tool.

Am I missing an option somewhere?

Thanks,
Thomas

[Thomas Augustin]

Hi Sebastian,

Do you have a URL, which has this problem, so we can reproduce this?

Well, use a proxy and then call e.g. http://www.whatismyip.com/ ... You'll see that they can show you your original IP (most prob done reading X-Forwarded-For, no?) but Firebug doesn't ...

Cheers,
t

[MiNi]

(picture from this link http://oxpedia.org/wiki/index.php?title=AppSuite:Grizzly#Multiple_Proxies_in_front_of_the_cluster )

http://en.wikipedia.org/wiki/X-Forwarded-For

this header is injected by the proxy, but its injected from FireFox

Sample Request

Route: FireFox --> Proxy --> WebServer
Route with injection: FireFox --> [ ProxyIn --> Proxy inject "X-Forwarded-For" --> ProxyOut ] --> WebServer


but this header is not in the response from webserver

[Thomas Augustin]

Route: FireFox --> Proxy --> WebServer
Route with injection: FireFox --> [ ProxyIn --> Proxy inject "X-Forwarded-For" --> ProxyOut ] --> WebServer

ok, i think i understand: because the request is not started from my browser with x-forwarded-for, firebug cannot see it. makes sense.

thanks,

t

[Sebastian Zartner]

Yes. Also, for verifying if there is an error in the Net panel display you can use Wireshark for comparison.

Sebastian