IssueTracker

Issue Summary : encountering an issue with one of the Google Cloud Functions where a custom header, "jwt_token", is not being passed through as expected.

- The customer encountered a problem within their project while deploying Cloud Functions. They were unable to pass the request headers as intended.
- In the user interface, they can see that the jwt_token has been passed to the backend (i.e., to Cloud Function). However, when they checked the logs, they noticed that the jwt_token header was missing and observed an error [1].
- Customer has confirmed that the request header “jwt_token” is being used perfectly in other projects as the functionality and code are similar, and recently they observed there are other projects as well whether this issue occurs but they haven’t known the reason for the issue..
- Customer  also confirmed that the code is working fine locally with the custom request header “jwt_token” and able to pass it to the backend and also they have observed that  jwt-token instead of jwt_token the token is getting passed in the backend but they don’t want that as the jwt_token is a custom token created for the functionality.
- Customers think that this should be related to the Cloud Function environment, and ask if there was any version change from Google's side.
Could you please check the issue and help the Customer with the resolution on request headers

Additional information :
- They even followed the third-party documentation [2] and still for other projects with similar issues it is working as suggested in the doc [2] but for this some projects it is not working
- Customer confirmed that they are re deploying in cloud function not in Cloud run, where they have their Jenkins job that push zip to Cloud Storage and deploy it using gcloud command [3]


____________________________________________
References :

[1] : “jwt_token header is not found”
[2]  :  https://stackoverflow.com/questions/78361018/google-cloud-function-headers-are-not-received-in-the-endpoint
[3] : gcloud --quiet functions deploy {{function_name}}-{{cluster_name}} --source=gs://eddata-{{gcs_bucket}}/{{gcs_folder}}/{{component_name}}-${BUILD_VERSION}.zip --trigger-http --project={{project_id}} --region={{region}}