kevinrenskers
commented
2 years ago Closed lhoang closed 2 years ago
kevinrenskers
commented
2 years ago 
BetaConnector
commented
2 years ago Same problem here. Running the node-server behind an nginx-ingress (microk8s) with the following settings:
ingress:
annotations:
nginx.ingress.kubernetes.io/proxy-buffer-size: "16k"
nginx.ingress.kubernetes.io/proxy-buffers: "16k"Still not doing the trick.
This is currently a show-stopper.
Rich-Harris
commented
2 years ago I'm going to close this as it's very easy to fix in userland:
export function handle({ event, resolve }) {
const response = await resolve(event);
response.headers.delete('link');
return response;
}It's also very easy to customise the header (for example, you could truncate it to a certain size, or omit the stylesheets, etc etc). By contrast, a config option would have to choose between simplicity (e.g. a boolean) and flexibility (size limits, filters) which would bloat the framework's surface area for very little gain.
lhoang
commented
2 years ago Thank you for your response. I should have thought of it. It does the trick.
BetaConnector
commented
2 years ago @Rich-Harris, if every big project results in this workaround, I think this should be fixed within the project and not by the user.
haikyuu
commented
1 year ago maybe creating a svelte-kit-big-project-plugin would do?
aakash14goplani
commented
3 months ago I'm going to close this as it's very easy to fix in userland:
export function handle({ event, resolve }) { const response = await resolve(event); response.headers.delete('link'); return response; }It's also very easy to customise the header (for example, you could truncate it to a certain size, or omit the stylesheets, etc etc). By contrast, a config option would have to choose between simplicity (e.g. a boolean) and flexibility (size limits, filters) which would bloat the framework's surface area for very little gain.
How to truncate header to a certain size?
Describe the bug
In our app, the pages contain a lot of components. Since the feature #5735 that turn the preload meta links into header links, we have response headers that are over 4ko. This causes the nginx in front of the sveltekit app to throw an error
upstream sent too big header while reading response header from upstream. My devops team would much prefer not to resize the header limit (1ko). Is there a way to opt out of the 5735 feature ?You can see the current meta links here (pre-5735) : https://www.francebleu.fr/
It has become in response headers :
Reproduction
https://github.com/lhoang/bug-headers
I tried to add more components, but for the sake of reproducing the bug, it would have been unnecessary and irrelevant.
npm run buildnode buildLogs
Severity
blocking an upgrade
Additional Information
Thank you for all your work and the amazing new changes in Sveltekit