DPDK CI discussions
 help / color / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 302] Google's Webcache version of the website does not work
Date: Mon, 01 Jul 2019 20:26:39 +0000
Message-ID: <bug-302-149@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=302

            Bug ID: 302
           Summary: Google's Webcache version of the website does not work
           Product: lab
           Version: unspecified
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: dashboard
          Assignee: ci@dpdk.org
          Reporter: jplsek@iol.unh.edu
                CC: jplsek@iol.unh.edu
  Target Milestone: ---

Google's Webcache version of the website does not save or dynamically load the
tables from Javascript.

For example:
https://webcache.googleusercontent.com/search?q=cache:AToLV55T2rcJ:https://lab.dpdk.org/results/dashboard/+&cd=1&hl=en&ct=clnk&gl=us

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
sites.

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
API.)

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-302-149@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=ci@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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 \
		ci@dpdk.org
	public-inbox-index ci


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/ public-inbox