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
encoded url causing error when accessing via static mode #8679
Comments
Hi @c53hzn actually it is not related to |
Hi @pi0 |
Hi, I'm sorry to bother you guys again on this issue. eg: This is the page that doesn't work Can anyone help me on this? |
@c53hzn, where you able to resolve your issue? i am seeing the same issue when my path includes a space |
I have Chinese URLs encountering the same problem. |
I think this was fixed in #9494 |
Versions
Reproduction
https://github.com/c53hzn/c53hzn.github.io/tree/master/_nuxt/static/1611255759/blog/language
This is how the generated paths look like
And the encoded format will cause error when relevant pages try to extract data from the payload.
Additional Details
Steps to reproduce
if I go to a page with Chinese characters in path, the payloads generated won't work because the paths generated for payloads with encoded characters need to be encoded again before the payloads can be accessed
eg:
If I want to access the payloads generated for this path:
c53hzn.github.io/blog/language/中文
The payload is stored in this path:
c53hzn.github.io/_nuxt/static/1611321880/blog/language/%E4%B8%AD%E6%96%87/payload.js
Here "%E4%B8%AD%E6%96%87" is the encoded Chinese character "中文"
But in order to access this payload, the actual URL should be
c53hzn.github.io/_nuxt/static/1611321880/blog/language/%25E4%25B8%25AD%25E6%2596%2587/payload.js
What is Expected?
Static mode should generate payload path as is, rather than generate encoded paths.
What is actually happening?
Encoded paths cause errors when fetching data.
I think it's the same issue as this one #8680, and I followed @pi0 's advice and updated Nuxt, but the issue remains.
The text was updated successfully, but these errors were encountered: