[BUG] The official website is experiencing problems with some externally referenced image presentation
Is there an existing issue for this?
- [x] I have searched the existing issues
Current Behavior
I found the #3124 already use local file to solve some problem, but the web still have some externally referenced image, maybe should modify the front strategy?
Expected Behavior
No response
Steps To Reproduce
No response
Environment
HertzBeat version(s):
Debug logs
No response
Anything else?
No response
It seems that the search function has also been blocked and is unavailable.
I think we need to check common external resource location
src/assets/
public/
config/webpack/
solution:
A[Detect External Resources] --> B{Critical?}
B -->|Yes| C[Convert to Local]
B -->|No| D[Remove/Replace]
C --> E[Add to assets/]
D --> F[Fallback UI]
This has only recently become like this. I checked the most recent commit and I feel that it nothing with the code, but with the cross-domain security policy of an external web server
hi yes, the cross-domain policy of the Apache website has changed. There is currently no good solution. We can only see if the administrator can restore the previous policy.
https://issues.apache.org/jira/browse/INFRA-26760
In addition to issues caused by cross-domain policies, there are also problems with other links.This is what I have discovered so far:
I will fix the above website links.
Hi, @tomsun28
I noticed that some screenshots contain TANCLOUD logo, do these screenshots need to be replaced? If so, we may need to create a new issue to track and handle this.
https://issues.apache.org/jira/browse/INFRA-26760
I'm curious as to why the images on the apisix official website are normal. https://apisix.apache.org/team/
I will attempt the following proposal:
- Add a JavaScript script to fetch GitHub avatar images from both member.json and .all-contributorsrc file, and then converting the avatar into base64 strings.
- Refactor the team page. In this version, the ALL-CONTRIBUTORS section will not directly generate HTML. Instead, it will maintain the same logic as the member section.
- Applicable to GitHub Action Workflow.
If there are no other questions, please assign this issue to me. I will try to raise a PR to achieve this proposal.