On Sun, Oct 21, 2018 at 08:58:26PM -0400, Thomas Dickey wrote: > I don't see any mention of -trace in the discussion (I'd start there, > to see what url's are actually fetched).
Hi, Regarding the "invalid cookie paths": >From the trace file, I have the following request-uri: GET /search?ie=ISO-8859-1&hl=fr&source=hp&q=tintin&btnG=Recherche+Google&gbv=1 HTTP/1.1 In server response, I have 2 cookies with an "invalid path attribute": /complete/search /search Lynx code seems to perform some prefix validation on the paths regarding the request uri, but it seems there is no such thing as path validation in the RFC: https://tools.ietf.org/html/rfc6265 Namely, /complete/search and /search path attributes should not block lynx acceptance of those cookies. regards, -- Sylvain
Lynx.trace.xz
Description: Binary data
_______________________________________________ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
