Hi there,
is there a specific reason you are hardcoding the cookie domain to a setting?
It seems to me that not setting the cookie domain explicitly would be easier, as it allows web.py to set the cookie domain to whatever the visitor is coming in from (That would certainly prevent the error that visiting 0.0.0.0:8080 as printed by web.py in the console doesn't allow a login, because the cookie domain ist set to localhost.)
This could come from the fact that you may be running con-go.net behind a proxy server (apache from the looks of it) which could mean that the original request server is lost when not explicitly communicated to web.py via an apache setting.
Is that the case? If not, I'd like to take this setting out to make the code simpler.
Hi there,
is there a specific reason you are hardcoding the cookie domain to a setting?
It seems to me that not setting the cookie domain explicitly would be easier, as it allows web.py to set the cookie domain to whatever the visitor is coming in from (That would certainly prevent the error that visiting 0.0.0.0:8080 as printed by web.py in the console doesn't allow a login, because the cookie domain ist set to localhost.)
This could come from the fact that you may be running con-go.net behind a proxy server (apache from the looks of it) which could mean that the original request server is lost when not explicitly communicated to web.py via an apache setting.
Is that the case? If not, I'd like to take this setting out to make the code simpler.