You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently set up a standalone React app deployment using mcr.microsoft.com/cbl-mariner/base/nodejs:18.18-cm2.0 in my Dockerfile. However, I encountered issues with server-side data fetching. Specifically, custom headers (e.g., an API version header) were being dropped, resulting in the v1 service response instead of the expected v2.
After downgrading to mcr.microsoft.com/cbl-mariner/base/nodejs:18.17-cm2.0, the issue was resolved.
Are there any known issues with nodejs:18.18-cm2.0 or higher versions regarding the Fetch API or header handling? If so, could you point me to the relevant release notes or documentation?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all,
I recently set up a standalone React app deployment using mcr.microsoft.com/cbl-mariner/base/nodejs:18.18-cm2.0 in my Dockerfile. However, I encountered issues with server-side data fetching. Specifically, custom headers (e.g., an API version header) were being dropped, resulting in the v1 service response instead of the expected v2.
After downgrading to mcr.microsoft.com/cbl-mariner/base/nodejs:18.17-cm2.0, the issue was resolved.
Are there any known issues with nodejs:18.18-cm2.0 or higher versions regarding the Fetch API or header handling? If so, could you point me to the relevant release notes or documentation?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions