File with Cyrillic in its name can't be sent #23

New issue

Closed

opened 2026-10-17 20:44:55 +00:00 by bmt · 1 comment

bmt commented

2026-10-17 20:44:55 +00:00

Member

build: anotherim-js 0.6.0

Sending File with Cyrillic fails with:"Failed to construct 'Headers': String contains non ISO-8859-1 code point"

steps:

Attach a file with Cyrillic letters in its name
Send it

expected: the file is sent with its name

actual: sending fails with a technical error in english

build: anotherim-js 0.6.0 Sending File with Cyrillic fails with:"Failed to construct 'Headers': String contains non ISO-8859-1 code point" steps: 1. Attach a file with Cyrillic letters in its name 2. Send it expected: the file is sent with its name actual: sending fails with a technical error in english

изображение.png

19 KiB

bmt added the

bug

windows

labels

2026-10-17 20:44:55 +00:00

ann referenced this issue from a commit

2026-10-18 10:26:07 +00:00

A file with a Cyrillic name could not be sent from the app (#23, 0.6.0: "Failed to construct 'Headers': String contains non ISO-8859-1 code point"): the page handed the file's bytes to the shell's file_put, file_keep and file_save with its name raw in an x-name header, Tauri's invoke makes that request with fetch, and fetch's Headers take ISO-8859-1 alone, so a Cyrillic or emoji name threw before anything was sent, on Windows, Linux and macOS alike; an accented Latin-1 name got past fetch only for the shell's to_str to refuse it as "x-name is not text". bodyHeaders now percent-encodes the name (encodeURIComponent) and ipc_body::name decodes it in files.rs, refusing a malformed escape or non-UTF-8 bytes; the XML console's own file_save goes through bodyHeaders too. The name the backend sends over XMPP (the upload slot request and the shared file's name) was always File.name passed beside the path, so it stays the original Unicode, as does the save dialog's suggestion before its own cleaning; the web build sends no file name in a header (its PUT carries the slot's headers and the content type). tauri-transport.test.ts sends a Cyrillic, an emoji, a quoted name with a semicolon and a 100%-with-é name through bodyHeaders into a real Headers and back through decodeURIComponent, and ipc_body.rs tests the decoding of the same shapes and the refusal of broken ones; the changelog says so.

ann commented

2026-10-18 10:35:23 +00:00

Owner

The page put the file name into an HTTP header as it was, and browser headers take only ISO-8859-1, so a Cyrillic or emoji name threw before anything was sent. The name is now percent-encoded and the shell decodes it; the name sent over XMPP stays the exact original.

Fixed in 0.6.1: https://dev.another.im/another-im/anotherim-js/releases/tag/v0.6.1

ann closed this issue

2026-10-18 10:35:23 +00:00