Status Update
No update yet.
Comments
va...@google.com
ku...@google.com
lu...@google.com
In the mean time, you can downgrade to Cloud SDK version 185 as a workaround by running the following command:
gcloud components update --version 185.0.0
ku...@google.com
Hello,
Thank you for reporting the issue.
I have just noticed that the product engineering team is aware of this issue and is currently working on it evaluating it in the best possible way. Above
Any further update will be communicated here. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued.Your feedback enables us to enhance our products and services. In the meantime, while we provide an update on this matter, I recommend reviewing the Stack Exchange links mentioned in
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
Description
How to reproduce:
On investigation, it appears that app engine does not return the content of the home page content. This appears to be related to the value of the if-mofified-since header. It seems to affect all browsers, including Chrome and Safari.
When a browser request the URL it passes an 'if-mofified-since' header. App engine will only return the page content if this value is set to 40 years more more in the past.
This curl command replicates a request from Chrome, in bold you see the mofified header:
curl '
-H 'authority:
-H 'accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7' \
-H 'accept-language: en-US,en;q=0.9' \
-H 'cookie: _ga=GA1.1.1403379917.1687631573; intercom-id-r70azrgx=4b984bfc-14d6-4415-8b47-44fd2dd02a5c; intercom-device-id-r70azrgx=8acbe93a-d072-4481-9145-781bc23809b4; _ga_BPLPFE2TCB=GS1.1.1692459914.85.1.1692459940.0.0.0; _ga_XFB3XT8XKQ=GS1.1.1692688923.14.1.1692689641.0.0.0' \
-H 'if-modified-since: Tue, 01 Jan 1980 00:00:01 GMT' \
-H 'sec-ch-ua: "Chromium";v="116", "Not)A;Brand";v="24", "Google Chrome";v="116"' \
-H 'sec-ch-ua-arch: "arm"' \
-H 'sec-ch-ua-bitness: "64"' \
-H 'sec-ch-ua-full-version-list: "Chromium";v="116.0.5845.96", "Not)A;Brand";v="24.0.0.0", "Google Chrome";v="116.0.5845.96"' \
-H 'sec-ch-ua-mobile: ?0' \
-H 'sec-ch-ua-model: ""' \
-H 'sec-ch-ua-platform: "macOS"' \
-H 'sec-ch-ua-platform-version: "13.0.1"' \
-H 'sec-ch-ua-wow64: ?0' \
-H 'sec-fetch-dest: document' \
-H 'sec-fetch-mode: navigate' \
-H 'sec-fetch-site: none' \
-H 'sec-fetch-user: ?1' \
-H 'upgrade-insecure-requests: 1' \
-H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/
--compressed
The above request returns no page content.
If the same request is made with an earlier if-mofified-since header, then the content of the page is returned.
What is the business impact you are facing?: Users cannot load our web app - so this is having a significant impact.
App Engine version: Standard Java 11.
After further investigation the following reason for this happening has been found:
The problem is due to AppEngine returning cached versions of the index.html page loaded via our servlet. There should be an option for the files timestampts to be set to the CURRENT TIME when the app is deployed and not left with a zero timestamp from the Webpack build.