Skip to content
This repository has been archived by the owner on Jun 19, 2023. It is now read-only.

Basic auth cookie handling #956

Closed
jesmrec opened this issue Nov 13, 2017 · 4 comments
Closed

Basic auth cookie handling #956

jesmrec opened this issue Nov 13, 2017 · 4 comments

Comments

@jesmrec
Copy link
Contributor

jesmrec commented Nov 13, 2017

Steps

  1. In server (basic auth), create a new account
  2. Upload several pics to this account in web UI
  3. In device, login in the account

Current behaviour

By checking the "Security" section of the user in webUI , we can notice something like this:

screen shot 2017-11-13 at 12 38 08

this is because some of the requests does not include in headers the cookies responsed by the server in previous requests.

Each time the server receives a requests with Authorization header and with no cookies, creates a new session.

Expected behaviour

Cookies are sent, so only a session is created for each User Agent

Testes with iPhone6Plus v10.0.1
Server 10.0.4

@nasli
Copy link
Contributor

nasli commented Nov 16, 2017

Fixed via owncloud/ios-library#168

@nasli nasli added this to the 3.7.0 milestone Nov 16, 2017
@nasli nasli added the Fixed label Nov 16, 2017
@jesmrec
Copy link
Contributor Author

jesmrec commented Nov 16, 2017

Working fine in OAuth2

@jesmrec
Copy link
Contributor Author

jesmrec commented Nov 16, 2017

In basic auth, each time the app is killed and reopened, a new row is created.

@nasli nasli mentioned this issue Nov 21, 2017
3 tasks
@nasli
Copy link
Contributor

nasli commented Nov 22, 2017

Handling of cookies has been refactored here #962 and now the cookies also going to be stored before the app will be killed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants