What does the noscript.ajaxFallback.enabled option in about:config do?
Basically, I have all google related scripts, including ajax related things, blocked. Surrogate support handles most issues related to that.
My main concern is that this option will somehow be bypassing the blocks.
In any case, what does noscript.ajaxFallback.enabled do?
Thanks!
noscript.ajaxFallback.enabled
noscript.ajaxFallback.enabled
Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20100101 Firefox/17.0
Re: noscript.ajaxFallback.enabled
Only thing I saw & maybe you can make sense of it?
"+ AJAX fallback support via Google's _escaped_fragment_ recommendation,
can be disabled by toggling the noscript.ajaxFallback.enabled preference
(see https://code.google.com/web/ajaxcrawling/, thanks alexbobp for RFE)"
"+ AJAX fallback support via Google's _escaped_fragment_ recommendation,
can be disabled by toggling the noscript.ajaxFallback.enabled preference
(see https://code.google.com/web/ajaxcrawling/, thanks alexbobp for RFE)"
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 SeaMonkey/2.21a2
Re: noscript.ajaxFallback.enabled
I did see that link referenced in noscript change logs before I made my original post, but I am not sure what it means. The linked page appears to be talking about how to make ajax sites/applications crawlable by search engines. Not sure what that would have to do with a setting in a browser.therube wrote:Only thing I saw & maybe you can make sense of it?
"+ AJAX fallback support via Google's _escaped_fragment_ recommendation,
can be disabled by toggling the noscript.ajaxFallback.enabled preference
(see https://code.google.com/web/ajaxcrawling/, thanks alexbobp for RFE)"
Thanks for trying to help!
Hopefully someone will have a better explanation of what the noscript.ajaxFallback.enabled preference does.
Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20100101 Firefox/17.0
- Giorgio Maone
- Site Admin
- Posts: 9454
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: noscript.ajaxFallback.enabled
This option just helps navigating some sites which strictly require JavaScript even without enabling it, by replacing the empty pages with their content-inclusive version designed for search engine indexing.
If your concern is security, this is innocuous.
If your concern is security, this is innocuous.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0
Re: noscript.ajaxFallback.enabled
After a quick read, I'm going to make an educated guess on this:
Some AJAX-based sites use a special query string syntax to advertise to crawlers that there is a way to retrieve a HTML snapshot of how the page would look after the AJAX executes.
NoScript is able to act like a crawler and use this to assemble the whole page without enabling JavaScript.
Some AJAX-based sites use a special query string syntax to advertise to crawlers that there is a way to retrieve a HTML snapshot of how the page would look after the AJAX executes.
NoScript is able to act like a crawler and use this to assemble the whole page without enabling JavaScript.
Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:22.0) Gecko/20100101 Firefox/22.0
Re: noscript.ajaxFallback.enabled
Giorgio and Thrawn,
Security was my concern, so thanks for the update about that.
I think I now understand what is going on, but I am curious about if it ever happens while I am browsing, and how often.
Not asking for a feature, but if there is an existing way to tell when the fallback happens in some kind of log, let me know. Or even an example of a site you know of where it would happen.
Thanks!
Security was my concern, so thanks for the update about that.
I think I now understand what is going on, but I am curious about if it ever happens while I am browsing, and how often.
Not asking for a feature, but if there is an existing way to tell when the fallback happens in some kind of log, let me know. Or even an example of a site you know of where it would happen.
Thanks!
Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20100101 Firefox/17.0