Yes, that's my point. ETags *require* quotes, but they're being removed. On Thu, Oct 29, 2020 at 9:25 AM Tamás Cservenák <ta...@cservenak.net> wrote:
> To me it seems does requite DQUOTE around it... > https://tools.ietf.org/html/rfc7232#section-2.3 > > Thanks > T > > On Thu, Oct 29, 2020 at 3:07 PM Nils Kilden-Pedersen <nil...@gmail.com> > wrote: > >> After debugging for a weird problem the entire day yesterday, I finally >> figured out why my ETag value was losing its quotes. For some reason, >> the innocently sounding HttpField.getValues apparently (needlessly?) >> appears to assume that comma separated header values might be quoted (not >> sure why, I don’t think it’s spec), and thus removes *required* quotes >> from etags, causing parsing failure later. >> >> So, e.g. this header: >> >> If-Match: "ab35ef1bc78", "5be73a9c523" >> >> will return invalid ETag values (unquoted). >> >> I would consider this a bug, but not sure why quote removal is even >> there, as I don’t see the HTTP spec requiring quotes around comma separated >> values. >> _______________________________________________ >> jetty-users mailing list >> jetty-users@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/jetty-users >> > _______________________________________________ > jetty-users mailing list > jetty-users@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list jetty-users@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
