Any thoughts here on whether or not the HTTP HEAD method should have a true mv_tmp_session? I'm kind of thinking it should since AFAIK HEAD is primarily used for link checking. Also, if a browser does both GETs and HEADs when a user visits a page (I think Safari does this sometimes, unless I'm seeing scripts with phony User Agents), a bunch of non-visited pages can show up in the session history. I'm not sure if this would simply boil down to having:$CGI::values{mv_tmp_session} = 1 if ("\U$CGI::request_method" eq 'HEAD');
in Server.pm in the else{} just after the POST and PUT conditions.
I'm quite concerned about what I could end up breaking, however.
Ideally, HEAD wouldn't eat as many system resources as GET, but
I'm not sure how easy it would be to have Interchange bail once
it knows the HTTP status code.
Any thoughts are much appreciated...
Thanks,
John Young
_______________________________________________
interchange-users mailing list
suppressed
http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.