Testing thread about nothing (I'm trying to diagnose an LQ-related Firefox issue)

test from work

Is there anybody out there?
http://www.youtube.com/watch?v=xACgZnt1wBo

Testing agent string Debian/Debian

Now setting everyplace it said linux to Debian, without the i686

Just plain annoying

Originally Posted by jiml8 Shouldn't be that hard. Just park wireshark on it and wait for the conditions of a duplicate post appearing - then check to see if a duplicate was sent out.

Hi Jim! Thanks for that suggestion;

I have discovered a workaround (provided I'm quick on the draw):

If I know my network is sloggy, and I've just clicked "Post Quick Reply" or whatever that button reads, I watch & wait while the java/vB/script does its thing trying to post my thread.

After waiting the mysterious amount of time my post to appear, and it doesn't (the problem occurs) then the STOP button lights up on my browser, indicating that the page is re/loading (hence re-submitting the dupe). At this instant, I hit STOP on the browser.

So at this point, I'm still on the same page, with my post still in the text field where I composed it; but if I now reload the current page, my post is actually there (submitted)! And the dupe has been stopped in its tracks.

Something server-side that might help in these circumstances, is if maybe LQ's "delay-between-posts" were increased. Right now I think it's 12 seconds (not sure) but maybe if it were increased, the post would not dupe, and instead LQ would tell me:

"You are trying to submit an identical post to one you have made within the last xx seconds. Please wait xx seconds."

I believe it's evident now that the submission is being made twice, and it's being allowed by the server. Not sure that Wireshark would add anything useful. Do you agree?

I'll link to this post from my S&F thread, maybe Jeremy will have something to say on it.

Sasha

In the user agent string for Iceweasel it should say "(Debian-3.5.1)" (or whatever your FF version is. If it doesn't, make it so!

testing...

Originally Posted by GrapefruiTgirl Hi Jim! Thanks for that suggestion; I have discovered a workaround (provided I'm quick on the draw): If I know my network is sloggy, and I've just clicked "Post Quick Reply" or whatever that button reads, I watch & wait while the java/vB/script does its thing trying to post my thread. After waiting the mysterious amount of time my post to appear, and it doesn't (the problem occurs) then the STOP button lights up on my browser, indicating that the page is re/loading (hence re-submitting the dupe). At this instant, I hit STOP on the browser. So at this point, I'm still on the same page, with my post still in the text field where I composed it; but if I now reload the current page, my post is actually there (submitted)! And the dupe has been stopped in its tracks. Something server-side that might help in these circumstances, is if maybe LQ's "delay-between-posts" were increased. Right now I think it's 12 seconds (not sure) but maybe if it were increased, the post would not dupe, and instead LQ would tell me: "You are trying to submit an identical post to one you have made within the last xx seconds. Please wait xx seconds." I believe it's evident now that the submission is being made twice, and it's being allowed by the server. Not sure that Wireshark would add anything useful. Do you agree? I'll link to this post from my S&F thread, maybe Jeremy will have something to say on it. Sasha

Wireshark might tell you why FF is reloading. Automatic reloads are not normal browser behavior, I don't think, though perhaps there is a FF setting that facilitates that. Perhaps some code is being returned from the LQ site that is prompting the behavior?

Originally Posted by jiml8 Wireshark might tell you why FF is reloading. Automatic reloads are not normal browser behavior, I don't think, though perhaps there is a FF setting that facilitates that. Perhaps some code is being returned from the LQ site that is prompting the behavior?

Ok, gotcha Jim -- I understand where you're going and after supper this evening, I will set Wireshark on the situation and see if I can learn anything. Thanks for your cont'd interest!

PS - I moved my/our "Beautiful Mind" posts to the 'movie' thread having taken your advice/sugg that it was somewhat off-topic.

Sasha

Ah - time to leave work and have a beer or 6.
TGIF

Testing, tap, tap, tap.

testing useragent again

Originally Posted by jiml8 Wireshark might tell you why FF is reloading. Automatic reloads are not normal browser behavior, I don't think, though perhaps there is a FF setting that facilitates that. Perhaps some code is being returned from the LQ site that is prompting the behavior?

I meant to mention too, that "auto-reloading" whether one considers it normal or not, can be done using <META-REFRESH> tags in HTML or PHP. However, I'd think that in the case of my problem here, that isn't what's happening.

Anyhow, I'll be soon getting Wireshark going, and will update later again.

Cheers.

Are you seeing actual additional gets in your firewall logs, or just firefox looking like it reloads? (or did I miss that in the previous 6 pages?)