Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backstage returns HTTP error code 304 on iPad and iPhone #8125

Closed
realsnick opened this issue Nov 18, 2021 · 6 comments
Closed

Backstage returns HTTP error code 304 on iPad and iPhone #8125

realsnick opened this issue Nov 18, 2021 · 6 comments
Labels
bug Something isn't working

Comments

@realsnick
Copy link

on iPhone and iPad backstage returns HTTP error code 304 and not loading

Expected Behavior

website should load fine

Current Behavior

website loads fine on PC/Mac but not on iPhone/iPad , did not test other devices.

Possible Solution

Steps to Reproduce

no link to a live example.

  1. Setup latest backstage on a server via docker
  2. Access website via iPhone or IPad - website will not load
  3. Access website via PC/Mac - website loads

Context

trying to setup a staging backstage instance via docker compose with backstage and postgress

Your Environment

on premise HP Server with 80 cpus , 512GB Ram and 2GB NVME

  • Operating System and Version Ubuntu: 20
  • Browser Information: chrome, safari (both on PC/Mac/iPhone and IPad)

I tried to clear cache on both safari and chrome on the iPad and iPhone though problem persists.

@realsnick realsnick added the bug Something isn't working label Nov 18, 2021
@realsnick
Copy link
Author

PS. Also tried in incognito mode on chrome.

@jhaals
Copy link
Member

jhaals commented Nov 18, 2021

Hi, sorry to hear that you're having issues. I tried this on locally running yarn start and setting app.baseUrl to http://0.0.0.0:3000 to get it to listen on all interfaces. I have no problems reaching the site on my iPhone.

@freben
Copy link
Member

freben commented Nov 18, 2021

I believe this may be related to #6039 . It will happen in all browsers on those devices since they are all forced to use the same underlying system web view component, if I recall correctly.

@jhaals
Copy link
Member

jhaals commented Nov 18, 2021

I managed to reproduce this on master and also purging yarn.lock. It's the same problem on Safari on Mac so freben is right that it's related to the issue linked.

@freben
Copy link
Member

freben commented Nov 18, 2021

Trying to put in place the (probably partial) fix proposed in the comment in that linked ticket: #8132

@freben
Copy link
Member

freben commented Nov 18, 2021

I'll close this as a duplicate, but thanks for reporting and it'll stay pointed to through the references in the "main" ticket.

@freben freben closed this as completed Nov 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants