[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-wget] [bug #52531] Content-Disposition parameter continuations shou

From: anonymous
Subject: [Bug-wget] [bug #52531] Content-Disposition parameter continuations should use filename*0*= not filename**0=
Date: Mon, 27 Nov 2017 08:44:21 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36


                 Summary: Content-Disposition parameter continuations should
use filename*0*= not filename**0=
                 Project: GNU Wget
            Submitted by: None
            Submitted on: Mon 27 Nov 2017 01:44:19 PM UTC
                Category: Program Logic
                Severity: 3 - Normal
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: None
        Operating System: None
         Reproducibility: Every Time
           Fixed Release: None
         Planned Release: None
              Regression: None
           Work Required: None
          Patch Included: None



fixed #44628 by supporting `filename*`.

It also introduced a new test:

{ "filename**0=\"A\"; filename**1=\"A.ext\"; filename*0=\"B\";\
+filename*1=\"B\"", "AA.ext", true },

This seems to be an attempt at implementing parameter continuations. Parameter
continuations are specified by [RFC 2231, section
4.1](https://tools.ietf.org/html/rfc2231#section-4.1). The following example
is given (edited with [errata](https://www.rfc-editor.org/errata/rfc2231)):

   Content-Type: application/x-stuff;
    title*2="isn't it!"

This shows two things:

1. The test should be `filename*0*=` instead of `filename**0=`.
2. When `filename*=` is used, the value should start with `encoding'language'`
(this is "ext-value" from RFC 5987). In practice some servers neglect to send
this prefix, so to be fault-tolerant it is okay to treat a missing prefix as
if the prefix was `''`.

This bug report is opened to suggest that 1 should be fixed.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]