* [dpdk-ci] [Bug 302] Google's Webcache version of the website does not work
@ 2019-07-01 20:26 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2019-07-01 20:26 UTC (permalink / raw)
Bug ID: 302
Summary: Google's Webcache version of the website does not work
Target Milestone: ---
Google's Webcache version of the website does not save or dynamically load the
This is because the CORS header 'Access-Control-Allow-Origin' is missing from
the server response.
A solution is to add the header with either a wildcard (*) or a list of allowed
Since the result of the fetch contains different information when logged in, I
don't think it's a good idea to use a wildcard (I'm not sure of the security
implications, if any).
A list of sites may be okay, but is there a specific list of trusted sites?
Another option could be to detect the bot server-side and fully return a
rendered page. (This could also add another benefit to CLI users, where a fully
rendered page is returned, but odds are, you'd probably want to use the REST
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, back to index
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-01 20:26 [dpdk-ci] [Bug 302] Google's Webcache version of the website does not work bugzilla
DPDK CI discussions
Archives are clonable:
git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/ public-inbox