Added note about the lack of language control via the Accept-Language

[sgryt]

HTTP header for FTN flows.

Inspired by https://app-eu1.hubspot.com/live-messages/24992676/inbox/14784443587#email

[netlify]

✅ Deploy Preview for criipto-docs ready!

Name	Link
🔨 Latest commit	eb4f741
🔍 Latest deploy log	https://app.netlify.com/projects/criipto-docs/deploys/68e63fe47bb39a0008276dfc
😎 Deploy Preview	https://deploy-preview-225--criipto-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[fkj]

I'm not sure this is correct? From a quick code inspection, FTN should also support using the Accept-Language header.

[sgryt]

I'm not sure this is correct? From a quick code inspection, FTN should also support using the Accept-Language header.

Could be - but seems to be what the reported problem suggests. I have not tried reproducing the issue, though (have no immediate tooling available for experimenting with signed requests)

[sgryt]

I'm not sure this is correct? From a quick code inspection, FTN should also support using the Accept-Language header.

Could be - but seems to be what the reported problem suggests. I have not tried reproducing the issue, though (have no immediate tooling available for experimenting with signed requests)

I agree that a quick code inspection indicates that this should still be supported (Accept-Language) - will try to repro tonight.