I guess we'd need to know what data the browser is providing to Symfony's
code to generate the session data. First glance through their docs, I
couldn't find anything viable.

On Tue, Dec 9, 2014 at 7:09 AM, Brian Teeman notifications@github.com
wrote:

OK this is a bit odd and you can ignore it if you want but perhaps it is
highlighting a bigger problem - I dont know

I am playing with the new web browser from yandex - which is based on
chromekit

Loading this site with yandex I get the following errors

Warning: SessionHandler::read(): The session id is too long or contains
illegal characters, valid characters are a-z, A-Z, 0-9 and '-,' in
/home/issuesj/vendor/symfony/http-foundation/Symfony/Component/HttpFoundation/Session/Storage/Proxy/SessionHandlerProxy.php
on line 69

Fatal error: Uncaught exception 'Whoops\Exception\ErrorException' with
message 'SessionHandler::write(): The session id is too long or contains
illegal characters, valid characters are a-z, A-Z, 0-9 and '-,'' in
/home/issuesj/vendor/symfony/http-foundation/Symfony/Component/HttpFoundation/Session/Storage/Proxy/SessionHandlerProxy.php:77
Stack trace: #0 [internal function]: Whoops\Run->handleError(2,
'SessionHandler:...', '/home/issuesj/v...', 77, Array) #1
#1
/home/issuesj/vendor/symfony/http-foundation/Symfony/Component/HttpFoundation/Session/Storage/Proxy/SessionHandlerProxy.php(77):
SessionHandler->write('', '_sf2_attributes...') #2
#2 [internal function]:
Symfony\Component\HttpFoundation\Session\Storage\Proxy\SessionHandlerProxy->write('',
'_sf2_attribu tes...') #3 #3
[internal function]: session_write_close() #4
#4 {main} thrown in
/home/issuesj/vendor/symfony/http-foundation/Symfony/Component/HttpFoundation/Session/Storage/Proxy/SessionHandlerProxy.php
on line 77

—
Reply to this email directly or view it on GitHub
#576.

Googled for it, but the only advice was to clean cookies :)

As its a bug in an alpha browser I guess we can close it?

I just brought it up as it might have highlighted a bigger issue

As its a bug in an alpha browser I guess we can close it?

I am not 100% sure that it is a bug in browser, but it looks like. Other browsers do not have this problem. So closing for now.