Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Bug: court report .docx download is blocked with a "virus detected" warning in Edge on Windows

Aperta
  • Qualcosa non va?
#7,104 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
rails, ruby
Ambito
backend

Direzione di ricerca

Inizia ritestando il rapporto giudiziario generato dopo il rilascio di #7098, usando Windows ed Edge, quindi esamina app/controllers/case_court_reports_controller.rb:22 e la pista di #7099. Confronta i download dei template default e Montgomery, verificando se rimangono residui di codici di campo. Il lavoro è completato quando il file .docx viene scaricato senza un avviso dell’antivirus o di SmartScreen e viene identificata la condizione responsabile.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

📊 Reports Help Wanted no-issue-activity Type: Bug

Reported by Voices for Children Montgomery in the 2026-08-07 stakeholder sync. Distinct from #7093 — see "Not the same bug as #7093" below.

Impacted User Types

  • volunteers, case supervisors, and org staff at the reporting org — multiple people, not one machine

Environment

prod. Microsoft Edge on Windows. Downloading a generated court report .docx.

Current Behavior

Generating a court report succeeds, but the browser download is blocked with a "virus detected" warning. The user has to go into their antivirus software and tell it to ignore the detection to download anyway.

Stakeholder's words, from the sync:

Every time I download a report and other people download a report, it says viruses are detected. And then I have to go into like the virus detection software to say to ignore the virus and download anyway … which is kind of obnoxious and that's been happening for a while [approximately six months].

[!NOTE]
Screenshot pending. A redacted screenshot of the Edge warning was captured during the sync and will be attached to this issue.

Expected Behavior

The generated .docx downloads without any antivirus or SmartScreen warning.

Not the same bug as #7093

#7093 was "the file isn't in the correct format" when opening the report in Word, root-caused to zip64 (#7098, shipped 2026-08-06). This one fires earlier — at download time, in the browser, before Word is involved — and the stakeholder dates it to roughly six months, whereas the zip64 regression only started when the caxlsx bump floated us to rubyzip 3.x in April 2026.

That said, #7098 shipped the day before this was reported, so step one is re-testing: a structurally odd zip (version-needed 45, 0xFFFFFFFF size placeholders) is exactly the sort of thing antivirus heuristics dislike, so the fix may have taken this with it.

Leads, cheapest first

1. The download has no explicit filename — see #7099. CaseCourtReportsController#show (app/controllers/case_court_reports_controller.rb:22):

@casa_case.latest_court_report.open do |file|
  # TODO test this .read being present, we've broken it twice now
  send_data File.read(file.path), type: :docx, disposition: "attachment", status: :ok
end

There is no filename:, so the browser derives the download name from the URL path. #7093 produced a file named _C-15-JV-24-191.docx — leading underscore, not in the case number. A binary attachment with a browser-derived name, served from a Heroku app domain with no SmartScreen reputation, is a good match for the heuristic profile. Fixing #7099 (File.binread + explicit filename:) is the cheapest thing to try and is worth doing regardless.

2. Field codes left in the generated document. The org templates are full of Word MERGEFIELD … \* MERGEFORMAT field instructions — visible in the raw XML of default_report_template.docx, and heavily throughout montgomery_report_template.docx (the reporting org's own template). Sablon substitutes the «…» text but the surrounding field-code machinery stays in the package. A .docx carrying field codes is a classic malware-delivery shape (DDEAUTO / INCLUDEPICTURE), and Defender is aggressive about it. Hypothesis, not verified — worth checking whether the generated output retains field-code remnants, and whether a template stripped of MERGEFIELD instructions downloads cleanly.

3. Ruled out. Content-Type is registered correctly — config/initializers/mime_types.rb maps :docx to application/vnd.openxmlformats-officedocument.wordprocessingml.document, so this is not a mismatched-type warning. Byte-exactness was verified during #7093/#7099 (Content-Length correct, download byte-identical to the stored blob), so it is not truncation in transit.

Info still needed from the stakeholder

  • Does it still happen now that #7098 has shipped (2026-08-06)?
  • Which antivirus is producing the warning — Windows Defender, or a third-party product?
  • Does Chrome or Firefox on the same machine warn too? (Separates the Edge/SmartScreen path from the AV engine itself.)
  • Does it happen for every org template, or only Montgomery's?

How to Replicate

Not reproducible on macOS or Linux — needs Windows + Edge, and ideally the org's real template rather than the default one (real templates from #6601's comments: prince_george_report_template.docx, montgomery_report_template.docx).

  1. Sign in as [email protected] / 12345678 on a Windows machine using Edge.
  2. Open a case with at least one case contact → Generate court report → pick a date range → Generate report.
  3. Click the resulting download link.
  4. Observe the "virus detected" warning instead of a clean download.

How to access the QA site

Login Details:
Link to QA site

Login Emails:

password for all users: 12345678

Questions? Join Slack!

We highly recommend that you join us in slack #casa channel to ask questions quickly. And discord for office hours (currently Tuesday 5-7pm Pacific), stakeholder news, and upcoming new issues.

Lingua principale
Ruby
Stelle
382
Fork
546
Merge medio
3g 5h
PR unite (30g)
9

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di rubyforgood/casa

Tutte le issue di rubyforgood/casa

Issue simili

Altre issue su Ruby

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.