Handle IE9/Netscape if-modified-since behaviour

See
http://stackoverflow.com/questions/12626699/if-modified-since-http-header-passed-by-ie9-includes-length
The first that spring to mind is cookies, eg.
Cookie: foo=bar; quo=baz
Going by the specs:
http://tools.ietf.org/html/rfc2616#section-14
I'd say that it's fairly common for http header values to use semi-colons
to separate additional parameters, but the exact usage is defined in the
specs on a case-by-case basis. Given that in most cases we would probably
want to keep these additional parameters, I'm not sure what the best
generalisation would be, or how useful it would actually be. Do you have
any suggestions for generalised procs?

-- 
Peter Chaplin
Qcode Software Limited
www.qcode.co.uk
T 01463 896 483


On 28 August 2014 10:48, Bernhard van Woerden <notifications@github.com>
wrote:

> In tcl/conn.tcl:
>
> > @@ -211,4 +212,12 @@ proc qc::conn_request_is_valid {request} {
> >          $
> >      }]
> >      return [regexp -expanded $re $request]
> > +}
> > +
> > +proc qc::conn_if_modified_since {} {
> > +    if { [ns_set find $headers If-Modified-Since]!=-1 } {
>
> I think this may generalis for any HTTP style headers using semi-colons.
> Are there other use cases ?
> eg
> header: blah; encoding=utf
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/qcode-software/qcode-tcl/pull/79/files#r16829986>.
>