Based on the information in the knowledge sources, there is no explicit documentation or community discussion about the specific "MalformedSecurityHeader" error when accessing an Elementary dashboard hosted on GCS via Firefox, while it works on Chrome. However, there are some relevant points from the community: - Access issues to GCS-hosted reports are often related to bucket permissions or the way the report is being accessed (public vs. private, direct file access vs. website hosting) [[Host the report on GCS](https://docs.elementary-data.com/oss/guides/share-observability-report/host-on-gcs)]. - Some users have reported browser-specific issues when accessing reports, but these were mostly related to rendering differences, not security header errors [[Slack thread](https://slack.com/archives/C02CTC89LAX/p1692848107076739)]. - The recommended way to host a report with a static, browser-accessible URL is to use the GCS bucket website feature and ensure the correct permissions are set. The URL should look like

<https://storage.googleapis.com/<bucket>/index.html>

[[Host the report on GCS](https://docs.elementary-data.com/oss/guides/share-observability-report/host-on-gcs)]. The error message you’re seeing suggests that Firefox may be sending a request header (possibly

te

) that is not expected or not handled by GCS in the same way as Chrome. This could be related to how signed URLs or authentication headers are being processed. What you can try: - Double-check that the GCS bucket is configured for website hosting and that the permissions allow access as intended. - Try accessing the report using the public website URL format (`https://storage.googleapis.com/<bucket>/index.html`) rather than the "cloud.google.com" file browser link, as the latter may require authentication and behave differently across browsers [[Slack thread](https://slack.com/archives/C02CTC89LAX/p1681378746901589)]. - If you are using signed URLs or private buckets, ensure that the method of generating and sharing the link is compatible with all browsers. If the issue persists, it may be a GCS-specific or browser-specific quirk not directly related to Elementary. In that case, you might want to consult Google Cloud Storage documentation or support for more details on header handling and browser compatibility. I'm sorry, but there is no direct solution to this specific error in the provided knowledge sources. If you need further help, you can reach out to the Elementary team via [Slack](https://elementary-data.com/community) for more targeted troubleshooting.