3 ms·
Our biggest challenge in building this tool was compatibility. Every webpage is different and even seemingly innocuous things things like frame busters and java
by dsiroker 16y ago
Our biggest challenge in building this tool was compatibility. Every webpage is different and even seemingly innocuous things things like frame busters and javascript redirects presented quite a challenge for us. We were fortunate to have a great set of early beta customers that gave us feedback when things didn't work and we took it one website at a time.
We'd love to share the lessons we learned along the way with the HN community in a blog post. Let me know what you're most interested in and we'll share what we've learned.
- photon_off 16y agoHow did you overcome frame busting and javascript redirects?
- SudarshanP 16y agohttp://en.wikipedia.org/wiki/Framekiller http://en.wikipedia.org/wiki/Framekiller may be useful. But I am curious about how it is done at Optimizely
- photon_off 16y agoThis is frame busting. I'm looking for anti frame busting. There's one way which involves calling a page which returns a "nothing" header code when the iframe tries to bust out. Though some sites like stackoverflow even take this into account. I wonder if SO works with optimizely (I'm on iOS, can't test it ATM). Since optimizely has access to the document, there might be a way to wrap the window.location object and prevent it from changing, before any experiment-site js is loaded.
- SudarshanP 16y agohttp://stackoverflow.com/questions/958997/frame-buster-buster-buster-code-needed http://stackoverflow.com/questions/958997/frame-buster-buste... This keeps getting funnier and funnier :)... that must be the state of the art in recursive busting ;-)... And if someone is so obsessed that his page must not be framed... I guess it is best to leave such a guy alone...