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.

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

Double maximum header length #2353

Merged
merged 1 commit into from
Oct 19, 2022
Merged

Double maximum header length #2353

merged 1 commit into from
Oct 19, 2022

Conversation

vinibrsl
Copy link
Contributor

Changes

This commit makes the permitted header length more permissive, 8,192 bytes, doubling the Phoenix default.

Related to 4lejandrito/next-plausible#67

Tests

I tried testing with ExUnit, but I could not reproduce the HTTP 431 Request Header Fields Too Large response. I guess this is because the HTTP server does not actually run in test environment. However, I tested this locally with curl and the HTTP 431 is fixed.

Changelog

  • This PR does not make a user-facing change

Documentation

  • This change does not need a documentation update

Dark mode

  • This PR does not change the UI

This commit makes the permitted header length more permissive, 8,192
bytes, doubling the Phoenix default.

Related to 4lejandrito/next-plausible#67
@vinibrsl vinibrsl requested a review from aerosol October 18, 2022 17:05
@bundlemon
Copy link

bundlemon bot commented Oct 18, 2022

BundleMon

Unchanged files (7)
Status Path Size Limits
static/css/app.css
515.19KB -
static/js/dashboard.js
295.97KB -
static/js/app.js
12.13KB -
static/js/embed.host.js
5.58KB -
static/js/embed.content.js
5.06KB -
tracker/js/plausible.js
748B -
static/js/applyTheme.js
314B -

No change in files bundle size

Final result: ✅

View report in BundleMon website ➡️


Current branch size history | Target branch size history

@vinibrsl vinibrsl requested a review from a team October 19, 2022 11:58
Copy link
Member

@aerosol aerosol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's revisit this once we start dropping unwanted headers earlier in the pipeline and/or nextjs gets this fixed.

@vinibrsl vinibrsl merged commit b898642 into master Oct 19, 2022
@vinibrsl vinibrsl deleted the increase-header-size branch October 19, 2022 12:41
vinibrsl added a commit that referenced this pull request Oct 26, 2022
This commit makes the permitted header length more permissive, 8,192
bytes, doubling the Phoenix default.

Related to 4lejandrito/next-plausible#67
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants