InformAction Forums

ever since the newest noscript update I am having problems logging into websites & posting to forums ect..?
does anyone else having this problem..?
I disabled the NoScript plugin and the Problem went away..
so what can I do to determine what exactly is causing this issue..?

I just tried previous versions of NoScript to see where the problem was first introduced and it appears to be in ( v 2.0.5rc3 )
because from ( v 2.0.5rc2 ) and below I don't encounter the problem at all..!!
https://addons.mozilla.org/en-US/firefo ... on-2.0.5.1

v 2.0.5rc3
==========================================================================
x Faster and more "correct" hack for internal redirections

v 2.0.5rc2
==========================================================================

What does this ( Faster and more "correct" hack for internal redirections ) do exactly, because for some reason it doesn't function well with my FF setup..
Is there anyway to disable it or something..?

In normal conditions the new internal redirections method should be more compatible, and I can see no way for it to cause a timeout.
Could you check whether this happens also ona clean profile with just NoScript installed?
If it doesn't, could you try Standard Diagnostic to spot a possible extensions conflict?
Thanks.

ScriptSh!t » Sun Nov 14, 2010 8:57 am
...I am having problems logging into websites & posting to forums ect..?
does anyone else having this problem..?
I disabled the NoScript plugin and the Problem went away..

If you are using the https option, be careful what you put in there under Force and Ignore. If not set up properly it can block logins.

This is odd, i just updated to NoScript 2.0.6rc1, and now the issue I was having is now gone..?
Wonder what the real issue was anyway..?

I'm having this same problem since updating to 2.0.5.1. After reading this topic, I tried 2.0.6.rc2, but that didn't help either.

Reverting to 2.0.4 did the trick for me, at least for now.

lüger wrote:I'm having this same problem since updating to 2.0.5.1. After reading this topic, I tried 2.0.6.rc2, but that didn't help either.

Could you be more specific about what the "same problem" is?
Which sites are affected?
Which actions are needed to reproduce?
Can you reproduce on a clean profile?
On a clean profile with just NoScript?
If you cannot, could you try Standard Diagnostic?
Thanks.

I'm experiencing a similar problem. But funny enough it's works like odd/even: so one post/submit works, the next one fails. I then have to trigger a get request to have the next post/submit work again.

When I deactivate NoScript, everything works as it should.

(I just got the same issue posting this reply! It triggered a 400 Bad request)

Giorgio Maone wrote:

lüger wrote:I'm having this same problem since updating to 2.0.5.1. After reading this topic, I tried 2.0.6.rc2, but that didn't help either.

Could you be more specific about what the "same problem" is?
Which sites are affected?
Which actions are needed to reproduce?
Can you reproduce on a clean profile?
On a clean profile with just NoScript?
If you cannot, could you try Standard Diagnostic?
Thanks.

The problem I'm having is that submit buttons simply don't work. I click them but nothing happens.
An example is eBay's signin page: https://signin.ebay.com/ws/eBayISAPI.dll?SignIn

A clean profile with the latest NoScript (2.0.7) had no issues, and after going through my extensions, I noticed that the problem only occurs when both NoScript and Xmarks are enabled. I'm using Xmarks 3.9.2.

However, a clean profile with only NoScript 2.0.7 and Xmarks 3.9.2 didn't have this issue, so the root problem is somewhere else.

For now, I've reverted back to NoScript 2.0.4 again.

lüger wrote: I noticed that the problem only occurs when both NoScript and Xmarks are enabled. I'm using Xmarks 3.9.2.

However, a clean profile with only NoScript 2.0.7 and Xmarks 3.9.2 didn't have this issue, so the root problem is somewhere else.

Could you use Standard Diagnostic while keeping both NoScript and XMarks enabled, so we can find the 3rd factor?

I disabled all other extensions, switched to the default theme and even disabled a few plugins, but the problem didn't go away.

lüger wrote:I disabled all other extensions, switched to the default theme and even disabled a few plugins, but the problem didn't go away.

Then is probably some specific setting in your regular profile.
Have you got pipelining or other network about:config preference set to non-default values?

It seems the problem finally went away

For some reason I don't recall, NoScript was configured to force HTTPS on *.xmarks.com. Removing that setting and restarting Firefox did the trick.

Thank you very much for your assistance!