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

hexo-offline should not register itself on terminating hexo s #93

Open
jerryc127 opened this issue Apr 17, 2019 · 1 comment
Open

hexo-offline should not register itself on terminating hexo s #93

jerryc127 opened this issue Apr 17, 2019 · 1 comment

Comments

@jerryc127
Copy link

能否设置hexo s 不 Caching static resource xxxx资源
而且关闭hexo s 又会在一次 Caching static resource xxxx资源

hexo g 会Caching static resource xxxx资源
hexo d 又会再一次Caching static resource xxxx资源

还有served via CDN
引用了https://cdn.jsdelivr.net/npm/velocity-ui-pack@latest/velocity.ui.min.js

options:
origin: 是写 cdn.jsdelivr.net/npm 还是cdn.jsdelivr.net

@JLHwung
Copy link
Owner

JLHwung commented Jun 6, 2019

Sorry for the late reply.

For the first question, hexo-offline should not inject itself during hexo s. So feel free to send a PR to correct that.

For the second question, the origin option is used as the origin request header when sw-precache is doing runtimeCaching. From the MDN docs here the origin header should conform to the following syntax

Origin: <scheme> "://" <hostname> [ ":" <port> ]

On your cases, it should be https://cdn.jsdelivr.net instead of cdn.jsdelivr.net/npm.

@JLHwung JLHwung changed the title 使用问题疑问 hexo-offline should not register itself on terminating hexo s Jun 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants