Tuleap 16 est là ! Assistez à l'événement virtuel le 17 octobre à 10h30. Inscrivez-vous ici !

    •  
      request #27187 Chrome-based browsers fallback on filename in HTTP headers
    Infos
    #27187
    Thomas Gorka (tgorka)
    2022-06-20 14:50
    2022-06-20 12:12
    28733
    Details
    Chrome-based browsers fallback on filename in HTTP headers

    When downloading files having non US-ASCII characters in their names, the downloaded documents have all their accentuated characters removed.

    When a file is being downloaded, the HTTP header contains two versions of the filename: filename and filename* where filename* uses the encoding defined in RFC 5987 and allows it to have non US-ASCII characters.

    However, the filename* is not parsed by some browsers, who are defaulting to the filename parameter.

    For instance, dépôt.log becomes dpt.log

    This issue occurs with Chrome-based browsers, such as Chrome, Chromium and Microsoft Edge.

    Empty
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Thomas Gorka (tgorka)
    Closed
    2022-06-20
    Attachments
    Empty
    References

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2022-06-20 14:50

    Integrated into Tuleap 13.9.99.155.


    • Status changed from Under review to Closed
    • Connected artifacts
    • Close date set to 2022-06-20
    User avatar
    Thomas Gorka (tgorka)2022-06-20 12:17
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Thomas Gorka (tgorka)2022-06-20 12:12
    • Summary
      -Chrome-based browsers fallback on filename in HTTP heeaders 
      +Chrome-based browsers fallback on filename in HTTP headers