You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But I think that this behavior is wrong and if a user has set an attribute, the default values should be applied where the user has not changed the data initially.
* Preparing request to http://localhost:3000/set
* Current time is 2020-11-27T11:34:50.035Z
* Using libcurl/7.69.1 OpenSSL/1.1.1g zlib/1.2.11 brotli/1.0.7 libidn2/2.1.1 libssh2/1.9.0 nghttp2/1.41.0
* Using default HTTP version
* Disable timeout
* Enable automatic URL encoding
* Enable SSL validation
* Enable cookie sending with jar of 1 cookie
* Found bundle for host localhost: 0x7fe8b77bf030 [serially]
* Can not multiplex, even if we wanted to!
* Re-using existing connection! (#4) with host localhost
* Connected to localhost (127.0.0.1) port 3000 (#4)
> POST /set HTTP/1.1
> Host: localhost:3000
> User-Agent: insomnia/2020.4.2
> Cookie: session_id=0462255d-4a43-4314-a982-b1e4d23694e6
> Accept: */*
> Content-Length: 0
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Fri, 27 Nov 2020 11:34:49 GMT
< Content-Length: 0
< Set-Cookie: cb98ba09-c8c4-4803-b8da-35e358174a0a; max-age=86400; path=/; SameSite=Lax
* Connection #4 to host localhost left intact
* Rejected cookie: Cookie failed to parse
* Saved 1 cookie
The text was updated successfully, but these errors were encountered:
Fiber version
Fiber v2.2.1
Issue description
If you use a non-standard config when initializing a session, it leads to the following consequences:
Set-cookie
becomes invalid because the field with the cookie name becomes""
Set-Cookie: cb98ba09-c8c4-4803-b8da-35e358174a0a; max-age=86400; path=/; SameSite=Lax
ID
is created for each request (by using code snippet do somelocalhost:3000/get
GET requests)btw isn't the UUID being incremented is a vulnerability?
This can be avoided if you fill in a little more information in a non-standard config. For example:
But I think that this behavior is wrong and if a user has set an attribute, the default values should be applied where the user has not changed the data initially.
For example config like this:
Should be like this on Fiber's backend:
Code snippet
Log
The text was updated successfully, but these errors were encountered: