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
Currently, if a user visits Invenio with an IPV6 address, the session will be invalid because it's not possible to extract correctly it's IP address after the changes (re-)introduced in 6459e40
Proper handling of IPV6 address must be introduced.
To reproduce the error just add in your /etc/hosts file something like:
::1 ip6-localhost ip6-loopback localhost
The browser will by default use ::1 when visiting localhost and this will trigger the session to be always invalid.
The text was updated successfully, but these errors were encountered:
#CommitTicketReference repository="" revision="c1389b21328131894408f6ba7549917a8ce589ec"
WebSession: IPv6 session handling fix
- When performing a request over IPv6, disable support for
CFG_WEBSESSION_IPADDR_CHECK_SKIP_BITS and directly
handle the full IPv6 address. (closes #1012)
#CommitTicketReference repository="" revision="c1389b21328131894408f6ba7549917a8ce589ec"
WebSession: IPv6 session handling fix
- When performing a request over IPv6, disable support for
CFG_WEBSESSION_IPADDR_CHECK_SKIP_BITS and directly
handle the full IPv6 address. (closes #1012)
#CommitTicketReference repository="" revision="c1389b21328131894408f6ba7549917a8ce589ec"
WebSession: IPv6 session handling fix
- When performing a request over IPv6, disable support for
CFG_WEBSESSION_IPADDR_CHECK_SKIP_BITS and directly
handle the full IPv6 address. (closes #1012)
Originally on 2012-04-17
Currently, if a user visits Invenio with an IPV6 address, the session will be invalid because it's not possible to extract correctly it's IP address after the changes (re-)introduced in 6459e40
Proper handling of IPV6 address must be introduced.
To reproduce the error just add in your /etc/hosts file something like:
The browser will by default use ::1 when visiting localhost and this will trigger the session to be always invalid.
The text was updated successfully, but these errors were encountered: