InformAction Forums

Hi.
When i browse into a filtered website, Noscript shows a alert on top of page. but when i set a proxy on Firefox and refresh page and Firefox loads filtered website, why Noscript alert doesn't hide automatically? (and i should click on close button (x) to hide the alert)

What kind of alert are you getting at the top of the page?

this type:

10.10.x.x is non-routable (& Local), right? So (& Local) would be the reason for the ABE warning.

(Will have to wait for others to comment on the rest.)

Saad wrote: but when i set a proxy on Firefox and refresh page and Firefox loads filtered website, why Noscript alert doesn't hide automatically? (and i should click on close button (x) to hide the alert)

Because the website is the same. It will hide as soon as the address changes.

Giorgio Maone wrote: Because the website is the same. It will hide as soon as the address changes.

Yes, but this is not a bug? i think when page refreshed it should hide and if was filtered show it again.

Hi,
for awhile Noscript can't block the content of filtered webpage.
i use Noscript 2.2.9rc1 .

Saad wrote:Hi,
for awhile Noscript can't block the content of filtered webpage.
i use Noscript 2.2.9rc1 .

What do you mean, exactly?

Please see: http://isaad.persiangig.com/Noscript_Fe ... ebpage.gif
i envisage this page be complete white and not load any content.
(i have disabled ABE alert: http://forums.informaction.com/viewtopi ... 741#p29528)

Did you know my purpose?

It is entirely possible that they're not using a local IP anymore, but an internet one (which is not enlisted in the LOCAL ABE ruleset).
What's the output of "ping www.facebook.com" issued in a terminal (cmd.exe) window?

Saad wrote:Please see: http://isaad.persiangig.com/Noscript_Fe ... ebpage.gif
Did you know my purpose?

لطفاً به من بگو کجا این اتفاق میافته و من سعی‌ می‌کنم که بهتر جواب تو را بدم

فکر می‌کنم که به فارسی بگی‌ راحت تره و من اگه لازم باشه با جورجو صحبت می‌کنم که چرا اتفاق میفته


Note: I believe the user to be a Farsi speaker, so I am going to try and engage him in his native tongue to hopefully facilitate the conversation and resolve any issues lost in translation.

ping www.facebook.com

Pinging www.facebook.com [69.171.229.11] with 32 bytes of d
Reply from 69.171.229.11: bytes=32 time=2412ms TTL=238
Reply from 69.171.229.11: bytes=32 time=2422ms TTL=238
Reply from 69.171.229.11: bytes=32 time=2538ms TTL=238
Reply from 69.171.229.11: bytes=32 time=2665ms TTL=238

Ping statistics for 69.171.229.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2412ms, Maximum = 2665ms, Average = 2509ms
---------------------------------------------------------------------------------
why when i type Farsi and click on submit, website show this error: ?
Ooops, something in your posting triggered my antispam filter...
Please use the "Back" button to modify your content and retry.

Saad wrote: Pinging www.facebook.com [69.171.229.11]

The DNS record seems correct, hence they're either forcing a proxy on you or they're directly injecting their alternative content inside responses.
Either way, ABE's LOCAL rule has no reason to be triggered anymore.

Just out of curiosity, does opening https://www.facebook.com (or even better putting .facebook.com inside your NoScript Options|Advanced|HTTPS|Force the following sites to use HTTPS box) work?

Saad wrote:why when i type Farsi and click on submit, website show this error: ?
Ooops, something in your posting triggered my antispam filter...
Please use the "Back" button to modify your content and retry.

Interesting, that should not happen as the site supports unicode text, so I am guessing some kind of misinterpretation. Giorgio any idea why he can't post his replies in Farsi so I an bridge the language barrier for him?

من با جورجو صحبت می‌کنم که چرا اجازه نمیده که فارسی بنویسی، فکر می‌کنم اشتباهه فوروم هست

tracert facebook.com
خواهش می‌کنم انجام بده و برای من به راه پی‌ام بفرست، شاید که یک پرکسی که میان ایران و بیرون وسط راه بأعث اشتباهه

tracert facebook.com

Tracing route to facebook.com [66.220.149.11]
over a maximum of 30 hops:

1 72 ms 102 ms 70 ms 2.182.32.1
2 69 ms 70 ms 70 ms 172.16.1.3
3 67 ms 102 ms 106 ms 217.219.106.125
4 80 ms 70 ms 78 ms 217.219.96.120
5 75 ms 70 ms 66 ms 217.219.96.132
6 95 ms 86 ms 102 ms 217.218.154.250
7 89 ms 90 ms 94 ms 10.10.53.30
8 230 ms 222 ms 222 ms 79.133.75.161
9 283 ms 270 ms 270 ms xe-7-2-0.frkt-ar2.intl.ip.rostelecom.ru [87.226.
133.58]
10 331 ms 334 ms 342 ms ae1.br01.fra1.tfbnw.net [80.81.194.40]
11 249 ms 254 ms 266 ms xe-2-0-0.br02.ams1.tfbnw.net [204.15.22.254]
12 332 ms 330 ms 334 ms ae6.br02.ams1.tfbnw.net [31.13.25.170]
13 409 ms 422 ms 410 ms ae16.bb01.pao1.tfbnw.net [204.15.22.252]
14 492 ms 494 ms 490 ms ae0.dr01.snc5.tfbnw.net [74.119.77.180]
15 500 ms 498 ms 498 ms po510.csw02a.snc5.tfbnw.net [74.119.78.22]
16 495 ms 506 ms 506 ms www-10-02-snc5.facebook.com [66.220.149.11]

Trace complete.