sitespeedio / sitespeedio/sitespeed.io

Add an option for dropping some headers from browser messages, from the har logs

Open
#4,526 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
5k
Forks
624
Avg merge
4h 8m
Merged PRs (30d)
2

Description

Feature/improvement

Summary

My web site use Authorization headers for all api requests. I would not like to save some headers into HAR or other data files. SiteSpeed v37.8.0 and Chrome-Har v1.0.1 don't have options for skipping specific headers and other sensitive filters:

  • authorization
  • cookie

Workaround 1

I'm getting a temporary token before the test, use the token for the test, and invalidate the token. My tokens are not actual as a result, but security filters don't know about tokens statuses. The security filters see the HTTP header Authorization in s3 and create an alert. I would not like to get the alerts. My workaround doesn't work well

Workaround 2

I'm thinking about getting browsertime.har.gz files from the s3 storage, removing some headers, and rewriting the browsertime.har.gz file in the storage. It will work well for existing data files.

Workaround 3

I can disable s3 options in sitespeed.io, sanitize har files, and upload all test results from my test pipeline into s3. It will work well for the new data files

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are named. Start by tracing how browser messages become HAR or browsertime.har.gz files and where SiteSpeed configuration is read, then inspect how Chrome-Har handles headers. Done means users can configure specific headers such as Authorization and Cookie to be excluded from generated data files, with coverage for the filtering behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
performance, security, tooling, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.