Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.ports.os2
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Why would site claim "10 minute timeout" after only 30-45 Seconds?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
MCGJr  
View profile  
 More options Nov 3 2012, 2:00 pm
Newsgroups: mozilla.dev.ports.os2
From: MCGJr <carl.gehr.NoSPAM...@mcgcg.com>
Date: Sat, 03 Nov 2012 14:00:11 -0400
Local: Sat, Nov 3 2012 2:00 pm
Subject: Re: Why would site claim "10 minute timeout" after only 30-45 Seconds?
Print | View thread | Show original | Report this message | Find messages by this author
On 10/18/11 09:16 pm, Carl Gehr wrote:
> On 09/30/11 09:27 pm, MCGJr wrote:

>> On 09/30/11 05:21 pm, Steve Wendt wrote:
>>> On 9/30/2011 1:15 PM, MCGJr wrote:

>>>> One secure site that I go to begins warning that it is about to log me
>>>> off for being idle for '10 minutes' even though I've only been on the
>>>> site for less than a minute. Clicking [OK] resets the timer for another
>>>> 30-45 seconds, but then the popup is there again.

>>>> Any idea what might cause this? And, hopefully, what might be done to
>>>> stop the problem?

>>> Sounds like this:
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=648360

>>> Try using SET NSPR_OS2_NO_HIRES_TIMER=1

>> Thanks! I've added the above. No chance to test yet. Bug ref was for
>> BofA site. I've seen it at both SunTrust and AmExp.
> I know it's been a while, but so far, the HIRES_TIMER approach seems to
> have worked.
> Thanks, again, for the suggestion.

The gremlins are back again  and even with:
> Rem **CG** Added following to try to stop premature SM Timeout. 30-Sep-2011
> Rem        Ref Bug 648360
> SET NSPR_OS2_NO_HIRES_TIMER=1

the sites above are back to premature timeouts.  Sometimes, even get
timeouts with transaction submissions less than five minutes old.

FWIW:  SeaMonkey is reporting itself as:

> Build identifier: Mozilla/5.0 (OS/2; Warp 4.5; rv:10.0.5) Gecko/20120603 Firefox/10.0.5 SeaMonkey/2.7.2

Yes, I know its a bit old, but the latest update is on the list for as
soon as I find my 'Round Tuit.'

Any new ideas or suggestions will be greatly appreciated.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google