Bug 89164
| Summary: | Need build.webkit.org to set CORS headers on some build results files | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | abarth, lforschler, simon.fraser, wsiegrist |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 84642 | ||
Simon Fraser (smfr)
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Adam Barth
> 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.
Lucas Forschler
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.
Lucas Forschler
This was fixed by changing the config file on the build.webkit.org apache server.
Simon Fraser (smfr)
This broke TestFailures: bug 89419