session.cookie_pathdefaults to '/', which is good. But if
session.cookie_pathis the empty string (''), then the cookie path is set relative to the current URL. If the request is to example.com/foo/bar/bax.php and the cookie path is '', then the cookie is set for example.com/foo/bar - not example.com/ as one might expect. But then the browser goes and saves it forever. And you can the same cookie id on multiple paths and then the expire and maybe some get reset during a logout/login cycle.
Suppose you have a database server (db.example.com) which only accepts connections from the web server (www.example.com). The web server accepts SSH connections from anywhere (so ssh firstname.lastname@example.org works). And you have 200 tables to update. Start by opening a tunnelled SSH connection in a terminal window like so: [shell]ssh email@example.com -L 31123:db.example.com:3306 [/shell] The command starts like a normal ssh connection.
Suppose your git development process uses lots of branching. Yay branching. You want to keep them all up-to-date with the master branch, but constantly merging master into a dozen or more branches is a bit of a pain. Here's one way: