"jekyll serve" CORS issue on some asset files

[reinhart1010]

Hello, I'm the creator of HAM, a very new Jekyll-based framework for creating static wiki sites. As of version 0.1.3 I have decided to include all external JS and CSS dependencies (e.g. Bootstrap Icons) into the /assets directory.

When serving with jekyll serve on Linux, some (local) asset files are not loaded in Google Chrome, and it seems to simply say "CORS Error". However, when serving the site with PHP and Python's development HTTP servers (php -S 127.0.0.1:4000 and python -m http.server 4000) over the generated /_site directory, these files are loaded properly.

Is this something related to Webrick's default configuration, and are there any solutions for this? I've also seen a feature request to allow modifying development server headers (#8785) and the issue doesn't seem to be resolved yet.

See also: reinhart1010/HAM#2

[mulingLHY]

I had the same problem when I used simple-jekyll-search. I found that the reason is that when I run "jekyll s", the site.url should be "127.0.0.1:4000"（defined in _config.yml）, but it is automatically replaced with "localhost:4000", so it causes " CORS Error".
Using http://localhost:4000/name instead of http://127.0.0.1:4000/name for local debugging can avoid this problem.

[jekyllbot]

This issue has been automatically marked as stale because it has not been commented on for at least two months.

The resources of the Jekyll team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the latest 3.x-stable or master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, please consider building it first as a plugin. Jekyll 3 introduced hooks which provide convenient access points throughout the Jekyll build pipeline whereby most needs can be fulfilled. If this is something that cannot be built as a plugin, then please provide more information about why in order to keep this issue open.

This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions.