Try and view the source • Hacker News Board

tomp wrote: post #56

sixcorners wrote: post #51

Earlier quoted context omitted.

Why is this possible? Is there a way to surpress this weirdness? I want to be able to trust my address bar again.

I believe that RTL character is one of the main failures of UNICODE. This should be part of the markup / rich text, not part of the plain text.

Even without the RTL directive, they might have used something like sourcе.html — which contains a non-ASCII glyph. So while RTL is problematic, I'm not prepared to call it a failure in that generally problematic space of unifying human communication.

Re: Try and view the source

#65

Post by cturner » Mon, Mar 19, 2012, 12:31 PM UTC

jrockway wrote: post #62

tantalor wrote: post #15

Earlier quoted context omitted.

You do know about `curl`, right?

Why use a popular utility when you can write your own in CoffeeScript !?

No need to be snide guys. If you don't know, you don't know. And there's no shame in trying.

Re: Try and view the source

#66

Post by twunde » Mon, Mar 19, 2012, 1:35 PM UTC

cute trick. I'll definitely use it as an extra security measure next time I'm working on something that leaks an id in the source

Re: Try and view the source

#67

Post by dazbradbury » Mon, Mar 19, 2012, 1:51 PM UTC

buro9 wrote: post #49

I hit F12 in Chromium, dev tools open with the tree, knowing that I'm viewing the DOM and not the source I hit the Resources tab, and there is the source. Not a problem at all. In fact, I had to remember to go back to right clicking and View Source to try and figure out why this was so highly ranked and lots of the comments confused me. Now I see why... but just like using JavaScript to try and detect right click, us…

> I bet someone does it on their live site.

I doubt it, as this method breaks forward/back functionality, thus probably breaking most sites.

Having said that, for all links, you could do a further re-write using the history API, before allowing the redirect to take place. I guess that would actually make it usable even if, as you say, it's futile in the end.

Re: Try and view the source

#68

Post by micheljansen » Mon, Mar 19, 2012, 1:52 PM UTC

twunde wrote: post #66

cute trick. I'll definitely use it as an extra security measure next time I'm working on something that leaks an id in the source

you mean an extra obscurity measure.

Re: Try and view the source

#69

Post by mkopinsky » Mon, Mar 19, 2012, 2:24 PM UTC

obtu wrote: post #59

Couldn't this have been done with a cookie and caching?

Ctrl-F5 would then cause the new page to show rather than the original.

Great idea though.

Re: Try and view the source

#70

Post by mkopinsky » Mon, Mar 19, 2012, 2:28 PM UTC

I loaded the page, went to Firebug script panel, set a breakpoint on the line of javascript, hit F5, when the breakpoint got hit, I just hit escape to prevent it from running. Then, Ctrl-U as usual.

Chrome is broken on my machine (proxy issues) so I didn't test there, but I assume the same technique would work.