Re: Don't Blame The Browser

I use HTTP::Proxy to monitor the connection between the browser and the server.

For doing web development that's not browser specific, I like using mozilla (or firefox). You can inspect the form specifically, by second clicking. left click for you lefties. Also, using liveheaders to get the parts you can't see is always helpful.

Bart: God, Schmod. I want my monkey-man.

Comment on Re: Don't Blame The Browser

Replies are listed 'Best First'.
Re^2: Don't Blame The Browser by drewbie (Chaplain) on Jun 11, 2004 at 02:55 UTC
And related to this, later versions of Mozilla (1.6+?) allow you to reload the View Source window w/o closing it, refreshing the browser, and viewing the source again. Quite handy when you're tweaking things and want a fast way to see your changes.	[reply]
Re^3: Don't Blame The Browser by samtregar (Abbot) on Jun 11, 2004 at 03:00 UTC
I tried to View Source after the browser was half-way baked. It nearly took down my entire machine. Memory usage shot past 600MB! -sam	[reply]
Re^4: Don't Blame The Browser by drewbie (Chaplain) on Jun 11, 2004 at 03:08 UTC
Holy cow! Consider me impressed! How long was the browser loading the page before you decided to view the source? I'm also amazed that apache didn't choke on the repeated hidden GET params before it got to that size. I thought I remembered reading about a limit of ~2k characters in a GET string? Looking through the HTTP/1.1 RFC I didn't see any mention, and I can't find it in the Apache docs either. Am I just remembering things?	[reply]
Re^5: Don't Blame The Browser by samtregar (Abbot) on Jun 11, 2004 at 05:22 UTC
Re^2: Don't Blame The Browser by samtregar (Abbot) on Jun 11, 2004 at 02:58 UTC
It's hard to use FireFox to inspect the form when FireFox is using 400MB of memory and won't respond to mouse input! -sam	[reply]