4 ms·
I wish View Source were more flexible. I would like: * Raw: a view of the actual body as sent in the response. Although I'm not aware of the current situation,
by oneeyedpigeon 10y ago
I wish View Source were more flexible. I would like:
* Raw: a view of the actual body as sent in the response. Although I'm not aware of the current situation, at least some browsers used to subtly alter what was sent, even for View Source (possibly related to validity corrections). I want a guarantee that what I'm viewing is what the server sent.
* View source as it is today (with a good common understanding of what that means), but a bit more powerful. Give me a cursor so I can copy from the keyboard, for crying out loud! Maybe even let me edit the source so I can work with static pages more easily.
* Something in-between View Source and DOM inspector. E.g. the original source, guaranteed to be untouched by javascript, but cleaned-up for easier reading (given that the source returned by many websites nowadays is practically unreadable (take a look at this page, for example). Reformatting (where possible), maybe automatic expansion of any base href, consistent ordering of attributes, highlighting of errors, etc.
- arethuza 10y agoIsn't a debugging proxy (like Fiddler) a good choice for the first of those?
- deleted 10y ago[deleted]
- LostCharacter 10y agoTo prevent a new browser request and to get a formatted version of the raw source in Chrome, you can open up the dev tools, go to sources, find the name of the page, and then click the curly brackets in the bottom left corner of the tools. It's still missing a good cursor implementation, though.
- nommm-nommm 10y agoDev tools in most browsers does the first as does Fiddler as mentioned in a sibling comment.
- db48x 10y agoHit F7 for caret browsing.
- eptcyka 10y agoYou can always use curl. Chrome allows you to copy paste a full curl command (with all the arguments and cookies) to issue an identical http request.