This is a snapshot of Indico's old Trac site. Any information contained herein is most probably outdated. Access our new GitHub site here.

Opened 6 years ago

Closed 5 years ago

#257 closed defect (wontfix)

Try to modify the back history to avoid login.cern.ch

Reported by: jbenito Owned by: jbenito
Priority: very low Milestone: v0.97.0
Component: General Version: 0.97.0
Keywords: Cc:

Description

Hi,

This has been bugging me for a long time and it seems I am not the only
one to suffer from this:

In LHCb, we have this extremely useful "meetings of the week" overview
page,
http://indico.cern.ch/categOverview.py?selCateg=1l22&period=week&detail=conference
Many of us use this as an extremely convenient entry point to indico.
When I then go to one of the meetings, I am typically asked for my "CERN
authentication", since most of our meetings are protected (as they
should be). So I log in and check the agenda of this meeting. Next, I
usually want to go back to the "meetings of the week" overview page to
check some other meeting. There is no "back" button in the web page so I
use the "back" button of my browser. But this does not work. Rather, I
get the annoying message:

------------


    Please wait at least 20 seconds between 2 logon attempts.

The request has been rejected because it appears to be a duplicate of a
request from this same client browser session within the last 20 seconds.

------------

although the overview page is NOT protected. And if I have the patience
to wait these 20 sec and then try again, I am taken to the indico home
page, not the LHCb "meetings of the week" overview page that I wanted to
get back to.

It would be extremely nice if this could be fixed.

 
Best regards,
Olaf Steinkamp

Change History (3)

comment:1 Changed 5 years ago by jbenito

  • Owner set to jbenito
  • Status changed from new to assigned

comment:2 Changed 5 years ago by jbenito

  • Status changed from assigned to in_merge

comment:3 Changed 5 years ago by jbenito

  • Resolution set to wontfix
  • Status changed from in_merge to closed

next version of shibb can make this problem less painful.

Note: See TracTickets for help on using tickets.