Opened 12 years ago

Closed 12 years ago

Last modified 8 years ago

#2002 closed bug (Invalid)

WebUI Auth not working in Safari 5 and Chrome 16 (on Mac)

Reported by: guard Owned by: damoxc
Priority: major Milestone:
Component: Web UI Version: 1.3.3
Keywords: Cc:

Description (last modified by Cas)

I'm using Deluge 1.3.3 through the WebUI accessible over the LAN In both Safari 5 and Chrome 16 I see the password form, and the following requests are being sent:

Request URL:
Request Method:POST
Request body: {"method":"auth.login","params":["*******"],"id":2}
Response body: {"id": 2, "result": true, "error": null}

Request URL:
Request Method:POST
Request body: {"method":"web.register_event_listener","params":["PluginDisabledEvent"],"id":3}
Response body: {"id": 3, "result": null, "error": {"message": "Not authenticated", "code": 1}}

Then 9 other json posts with the same response, and the page is reloaded with the same login form

Change History (5)

comment:1 Changed 12 years ago by johnnyg

Is the server's time correct?

If the time is incorrect then the login will reappear as safari/chrome thinks the cookie has expired.

comment:2 Changed 12 years ago by guard

it works in FF from the same machine

comment:3 Changed 12 years ago by Cas

  • Component changed from other to webui
  • Description modified (diff)
  • Milestone changed from Future to 1.3.x
  • Owner set to damoxc

I just tested with Chrome 16.0.912.63 and Safari 5.2.1 on Windows and have not seen any login issue.

comment:4 Changed 12 years ago by guard

  • Resolution set to invalid
  • Status changed from new to closed

OK, got it - going to close the ticket.

So, the reason was actually in cookie expiration - its set for 1 hour, the server is running Ubuntu with proper time settings, so if it's 9 PM in Minsk it's 6 PM GMT, and the cookie is set to expire at 7 PM GMT But at my machine I had to tweak the time manually 'cause Apple didn't issue patch to support our timezone yet (our country eliminated daylight saving recently), so the time was set manually to 9 PM while the timezone was still EET, which was read as GMT+2, so the actual time was considered as 7 PM GTM.

Long story short, I switched to a different TZ with offset +3, and now Deluge works just fine.

comment:5 Changed 8 years ago by Cas

  • Milestone 1.3.x deleted

Milestone deleted

Note: See TracTickets for help on using tickets.