Recent submissions

Comment · 14 years ago
Comment · 14 years ago
It's [406] "not acceptable" to register more than one view per haxx!
Comment · 14 years ago
If you wouldn't mind, please send me an email with your browser: [email protected]

Thanks heaps!

Comment · 14 years ago
I do my best by forwarding the client through with x-fowarded-for however it's completely up to the provider.

That said there's nothing to stop the haxx disabling/hiding ads or the visitor running Adblock for that matter.

Comment · 14 years ago
I've given some thought to that - it uses the same mechanisms as jsfiddle (different domains) and you can view the haxx code. As such CSRF should be fine and SSL isn't supported on public haxxlies.

I however, wouldn't recommend signing in through the service :)

Comment · 14 years ago
Yep. Private plans + a whole raft of other features I didn't have time to implement (SSL support, regex substitution on html, basic auth support etc etc). Any other suggestions?
Comment · 14 years ago
On what particular URL? Depending how servers are configured they may not like haxx.ly.
Comment · 14 years ago
It should be as good as jsfiddle.

The haxxlys run in an iframe on a separate domain to haxx.ly (similar to jsfiddle) to prevent you from hacking haxxly with haxxly.

You could use it to phish with but there is a giant banner saying this website is from haxxly and is altered. Also you can view the code yourself and flag it if it's bad.

Comment · 14 years ago
The actual code for that haxxly doesn't do anything (well - it attempts to load jquery and sets the font tag to arial). Check out http://www.haxx.ly/h/28 for a quick example.

The 406 is the view counter just reporting you've viewed the page. The script error was an error on that particular haxxly.

Comment · 14 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton