Aglet

Investigate downloaded filename changes across representations

Investigation should follow one document through each naming boundary and compare multiple representations. Use names with Unicode, punctuation, long text, and revision markers, then inspect the delivered bytes as well as labels. The brief should distinguish naming transformation from wrong content.

Build a useful investigation brief

  1. Build naming fixtures

    Prepare documents with spaces, non-ASCII characters, punctuation, repeated titles, and revision suffixes. Request the source and another supported representation, recording the expected saved names and document identity before download.

  2. Trace name construction

    Capture the display title, selected revision, format choice, response name, local saved name, and any collision suffix. Mark where characters, extension, case, or revision text changes, and keep the corresponding content identity beside each name.

  3. Compare content and labels

    Open or inspect the downloaded bytes and compare them with the selected document while reviewing the name transformation. If content is correct but the name differs, state the naming rule; if content differs, route identity evidence separately.

What to carry forward

The investigation is sufficient when a naming fixture identifies the first transformation and confirms whether bytes remain bound to the selected document. If local save behavior is not observable, report the response name and the unresolved client-side transformation.

Technical background: RFC Editor reference.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow