403 on sign in if running Airsonic on the same hostname/ip
popeen opened this issue · comments
Problem description
It seems something in the cookie is causing a 403 when signing in if you where previously signed in to an Airsonic instance on the same hostname/ip. Most likely it would be the same with other forks as well. My guess is that it is because of JSESSIONID being incorrect but this needs to be verified.
If you reload the page and then sign in again it will work, it will also work if cookies are cleared.
Steps to reproduce
- Run Booksonic Air
- Run Airsonic on another port
- Sign in to Airsonic
- Sign in to Booksonic
System information
- Airsonic version: 2009.1.0