Bug 89164 - Need build.webkit.org to set CORS headers on some build results files
Summary: Need build.webkit.org to set CORS headers on some build results files
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 84642
  Show dependency treegraph
 
Reported: 2012-06-14 22:06 PDT by Simon Fraser (smfr)
Modified: 2012-06-18 21:54 PDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Fraser (smfr) 2012-06-14 22:06:21 PDT
build.webkit.org needs to return a Access-Control-Allow-Origin: * header for full_results.json files (and maybe other files)?

We should ask the chromium guys how http://build.chromium.org is configured.

This is required for garden-o-matic to work on Apple bots. See bug 84642.
Comment 1 Adam Barth 2012-06-15 09:57:12 PDT
> We should ask the chromium guys how http://build.chromium.org is configured.

I think build.chromium.org just returns Access-Control-Allow-Origin: * for everything.  Nothing on there is secret.
Comment 2 Lucas Forschler 2012-06-15 10:49:18 PDT
I've created a .htaccess file which sets the header in webkit's public_html dir.  But, it does not appear to solve the problem.  It looks like buildbot is serving this page, not apache.
Comment 3 Lucas Forschler 2012-06-15 13:54:36 PDT
This was fixed by changing the config file on the build.webkit.org apache server.
Comment 4 Simon Fraser (smfr) 2012-06-18 21:54:05 PDT
This broke TestFailures: bug 89419