Re: "Fragment" request header

Hi Rob,

A lot of sites have been coded with the assumption that the fragment is a
safe place to stuff data that explicitly won't be sent to the server (in
fact that's why AJAX sites started using #! -- seems odd that now you want
to send it). Before postMessage() it was even used as a message-passing
mechanism. Changing this is not backwards compatible in the big picture.
Maybe as an opt-in, but if a site wanted to opt-in why wouldn't they just
change their URLs to put the bit they want to share in front of the #
instead of after?

When do you propose the fragment be sent? Would it start triggering loads
on each transition in an site that uses "#!" ? Or are you proposing to only
send it when current algorithms would trigger a load?

-Dan Veditz