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
In CAP Node.js version 7.9.1, I noticed that cds.context.headers and cds.context.http.req.headers were both populated with all request headers (see screenshots below).
version
in debug
However, starting from version 9+, I can see that cds.context.headers no longer contains all request headers, while cds.context.http.req.headers still does (see screenshot below).
version
in debug
I searched the documentation but couldn’t find any note about this change (see attached screenshots).
Is this an expected behavior in the newer versions, or is it a bug?
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
Uh oh!
There was an error while loading. Please reload this page.
-
Hello
In CAP Node.js version 7.9.1, I noticed that cds.context.headers and cds.context.http.req.headers were both populated with all request headers (see screenshots below).
version
in debug
However, starting from version 9+, I can see that cds.context.headers no longer contains all request headers, while cds.context.http.req.headers still does (see screenshot below).
version
in debug
I searched the documentation but couldn’t find any note about this change (see attached screenshots).
Is this an expected behavior in the newer versions, or is it a bug?
Beta Was this translation helpful? Give feedback.
All reactions