[idea] add Frontend Bundlers about blazer HOT 7 CLOSED

Hi, @ankane
Thanks for your response!

The file is blazer html.

blazer html have a link field in Response Headers which have many preload links.

That's why I got an error on Nginx.

Of course, I can solve this error by increasing the buffer size(ref), but there is a better option like this issue title

from blazer.

Hey @rikoroku, which files get that error?

from blazer.

Hey @rikoroku, it looks the page is returning a 200. Can you paste the nginx logs (with any sensitive info removed)?

I don't think a bundler should be needed (we can switch to minified assets instead), but I'm not sure how common the issue is, so probably won't make any changes now.

from blazer.

It looks like the largest asset file is under 1MB, which nginx should have no problem serving, so seems like something else may be going on.

from blazer.

I'm using Propshaft and I'm having the same issue. I can see in the logs the rails app returns a 200 on the /blazer route but then nginx throws a 502 Bad Gateway, nginx logs only say:

*3436865 upstream sent too big header while reading response header from upstream

I'm not able to see anything from the response in the browser.

from blazer.

Maybe the more feasible solution is using the import-map approach since I can tell there is no need of compilation of the blazer assets since they all are vanilla css and js.

from blazer.

Ah, didn't understand the issue earlier. It looks like Rails expects proxies to be able to handle up to 8,000 bytes. The value is currently hardcoded, but it'd be good to submit a PR to Action View to make it configurable for those who need this (since it can affect more than just Blazer). Another option for users is to disable the Link header:

config.action_view.preload_links_header = false

from blazer.