@dargmuesli is attempting to deploy a commit to the Nuxt Team on Vercel.

A member of the Team first needs to authorize it.

npm i https://pkg.pr.new/@nuxt/content@3701

commit: d44d5cd

No actionable comments were generated in the recent review. 🎉

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Forwarding all headers can make the fetch request return data with brotli compression which is not expected at the moment.

@dargmuesli Can't we just enforce Accept-Encoding to gzip, deflate or dropping that header? If it's only about brotli, we can simply drop the header!

@farnabaz - I have tested simply overwriting the header of Accept-Encoding in the nuxt.config routeRules but when running in production mode, since v3.11.x whenever using server side rendering, the following errors are still always returned. I even tried removing the header completely -

Route Rules:

routeRules:{
		'/__nuxt_content/**':{
			headers: {
				'Accept-Encoding': 'gzip, deflate' // or just '' to remove
			}
		}
}

Errors:

Database integrity check failed TypeError
 code: 'Z_DATA_ERROR',
  [cause]: Error: incorrect header check
...
[request error] [unhandled] [POST] http://localhost:3000/__nuxt_content/{contenttype}/query?v=v3.5.0--xAjoPoXoSfYkJiTVHdgWAiZ4y8fccTFopoR-DtcwS4s
 SqliteError: no such table: _content_...

As a note frontend once the page is loaded and navigating nuxt content works as expected but SSR is still broken

@obj63mc Could you try to monkey patch in node modules and test?

So testing this - as the code is set in v3.11.x - when passing all headers the following are passed -

 accept: 'text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7',
'accept-encoding': 'gzip, deflate, br, zstd'

Using the fix in this PR and only passing cookie header the headers are

accept: 'application/json'

If I hard code to delete the accept-encoding header just after the creation of the fetchOptions runtime/internal/api.js with -

delete(fetchOptions.headers['accept-encoding']);

then this functions as it should.

I also tried just overwriting the header in the nuxt.config routeRules but that would not work and is being ignored.
So my recommendation is if you simply want to pass all headers we either need to manually remove the accept-encoding header or set it to something that will work like -

'accept-encoding': '*'

I'm currently testing another fix related to compression, will update you when I got the results and check the solution proposed above too of course.

Are there any workarounds until a proper fix is made?

I currently have not found a way to work around this other than to run version 3.10 or by editing the internal/api.js file manually in node modules.

You can pnpm patch dependencies, I'm sure there is similar functionality for other package managers. See my patch here: https://github.com/maevsi/vibetype/blob/372ce28eacbb646bdbaa2135cdfbb827eae72baf/patches/%40nuxt__content.patch

Just FYI for anyone here who needs it before this gets resolved, as a possible workaround you can also disable the nitro.compressPublicAssets option if you have it enabled.

Of course this means that all compression will be disabled in production for you, so I'd only recommend this workaround if you have a low traffic site!