Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(host): Don't add unescaped meta headers to custom headers #136

Merged
merged 1 commit into from
Nov 23, 2023
Merged

fix(host): Don't add unescaped meta headers to custom headers #136

merged 1 commit into from
Nov 23, 2023

Conversation

Frederick888
Copy link
Owner

@Frederick888 Frederick888 commented Nov 23, 2023 •
edited by github-actions bot
Loading

Changes

a1fe40e fix(host): Don't add unescaped meta headers to custom headers

Checklist

  • I have rebased my branch so that it has no conflicts
  • I have added tests where appropriate
  • Commit messages are compliant with Conventional Commits

Is this a breaking change?

No

Test results

  • OS: Linux
  • Thunderbird version: 115

@Frederick888 Frederick888 force-pushed the fix-unescaped-meta-headers branch from d5ecc38 to 9bee69e Compare November 23, 2023 13:26
@Frederick888 Frederick888 force-pushed the fix-unescaped-meta-headers branch from 9bee69e to a1fe40e Compare November 23, 2023 13:35
@Frederick888 Frederick888 merged commit cffbe76 into master Nov 23, 2023
11 checks passed
@Frederick888 Frederick888 deleted the fix-unescaped-meta-headers branch November 23, 2023 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@Frederick888