Chrome, but not Firefox, appears to try and fetch favicon.ico and if it doesn't exist (and hits the 404) it is creating a new session id in the database table. Easy to work around this but still rather strange - we should have some sort of early-out for this.
Chrome, but not Firefox, appears to try and fetch favicon.ico and if it doesn't exist (and hits the 404) it is creating a new session id in the database table. Easy to work around this but still rather strange - we should have some sort of early-out for this.