[PAGES-532] CORS error on cached resources on chromium-based browsers Created: 02/Nov/21  Updated: 18/Nov/21  Resolved: 11/Nov/21

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.12

Type: Bug Priority: Neutral
Reporter: Robert Šiška Assignee: Lam Nguyen Bao
Resolution: Fixed Votes: 0
Labels: VN-Analysis, VN-Implementation
Remaining Estimate: Not Specified
Time Spent: 1d 5.5h
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Epic Link: External SPA
Sprint: HL & LD 41
Story Points: 3

 Description   

Steps to reproduce:

  • Ensure magnolia.develop=false
  • Clean browser cache before testing
  • CORS is enabled for external (uris: /.rest/, /VAADIN/)
  • Open SPA page with baseUrl config on chromium-based browsers

Expected results:

  •  Icon for green bar is shown, there's no CORS error on console

Actual results:

  •  Icon for green bar does not shown, there're CORS errors on console

Generated at Mon Feb 12 06:19:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.