network profile
| bio | website | xenotaph.net |
|---|---|---|
| location | United Kingdom | |
| age | ||
| visits | member for | 1 year, 7 months |
| seen | Apr 19 '12 at 15:13 | |
| stats | profile views | 12 |
In-house web monkey primarily working on the LAMP stack (Linux (Slackware), Apache, MySQL and PHP) and sometimes C#, Java and Perl on the side. I probably know more about Regular Expressions than is healthy and have a certain level of ninja skill with mod_rewrite.
(X)HTML, XML, JavaScript, JSON (AJAX) and CSS pretty much go without saying - and I think anyone who tries to sell you SEO as some kind of dark art is a snake oil salesman (make it work in Lynx, follow WAI guidelines and it'll pretty much BE search engine optimised by default).
|
Oct 25 |
comment |
Session cookie being dropped when moving under the SSL ... actually - I'd covered all those bases - but I think I've just solved it; and I think I may have done something a little daft ... You did point me in the direction of taking another, really good look at my session handling object though - thanks! :) |
|
Oct 24 |
comment |
Session cookie being dropped when moving under the SSL Might not have quite solved it ... but +1 on the Fiddler comment (I'd completely forgotten about it); there's definitely something strange going on as it seems the devSID cookie is being reset 3 times under the SSL shell - which shouldn't be possible as session_start() is called in a private constructor in a Singleton pattern! |
|
Oct 24 |
comment |
Session cookie being dropped when moving under the SSL Umm - no, basically. You can quite happily pass a cookie with the domain .mydomain.ext between https://secure.mydomain.ext and http://www.mydomain.ext - the worst that will happen is that something like McAfee Secure might report it as a low level security vulnerability (unencrypted cookie accessed in secure domain)... cookies aren't that clever. |
|
Oct 21 |
comment |
Session cookie being dropped when moving under the SSL Nope - it's something much stranger than that... I'm beginning to narrow it down to either something Windows XP specific or something to do with our office network - because it'll work fine on a Windows 7 machine outside this network I discovered last night; it might be some kind of domain conflict with our VPN to Holland but I'm not sure. I think this might turn out to be too case-specific to really be solved on stackexchange :\ |
