I’ve got an odd question. Are qovery inbound requests treated differently?
For some reason, the same exact app with the same exact Dockerfile works correctly on Heroku but on Qovery a header that’s added at runtime (from the frontend) is passed to the request but for some reason, the backend does not have that header while is does (as expected) on the Heroku counterpart
specify here your dockerfile content
# Use the official lightweight Node.js 14 image. # https://hub.docker.com/_/node FROM node:14-alpine # Create and change to the app directory. WORKDIR /usr/src/app # Declare env variables. ENV PORT 80 ENV HOST 0.0.0.0 # Copy application dependency manifests to the container image. # A wildcard is used to ensure both package.json AND package-lock.json are copied. # Copying this separately prevents re-running npm install on every code change. COPY package*.json ./ # Install dependencies RUN yarn # Copy local code to the container image. COPY . ./ # Expose the port EXPOSE 80 # Build the application RUN yarn build # Run the web service on container startup. CMD [ "yarn", "start:prod" ]