CAP, CORS and custom headers

The @sap/approuter has full support for CORS but I wanted to find out about what CAP offers and how to extend it. Specifically, this exploration was made with @sap/cds at version 7.8.0.

Test service

Before diving in, let’s create the simplest server that could possibly work1 to explore CORS support in CAP. First, a minimal project:

# /home/user/work/scratch
; cds init corstest
&& cd $_
&& rm -rf .vscode/ app/ srv/ db/ README.md
&& tree -a
Creating new CAP project in ./corstest

Adding feature ‘nodejs’…

Successfully created project. Continue with ‘cd corstest’.
Find samples on https://github.com/SAP-samples/cloud-cap-samples
Learn about next steps at https://cap.cloud.sap
.
|– .cdsrc.json
|– .eslintrc
|– .gitignore
`– package.json

1 directory, 4 files

Now, just the simplest test REST style service. In services.cds2:

@protocol: ‘rest’
service corstest {
function go() returns String;
}

And in the default implementation file for this service file, i.e. services.js:

module.exports = (s) =>
s.on(‘go’, () => `Hello, World!`)

Let’s also install the runtime locally with npm install (as we’ll want to look into one of the files there later), and start the server up with cds watch. Now we can perform a basic test, asking for verbose output3, to see what we get:

# /home/user/work/scratch/corstest
; curl –verbose –url localhost:4004/rest/corstest/go
> GET /rest/corstest/go HTTP/1.1
> Host: localhost:4004
> User-Agent: curl/7.88.1
> Accept: */*
>
< HTTP/1.1 200 OK
< X-Powered-By: Express
< Content-Type: text/plain; charset=utf-8
< Content-Length: 13
<
Hello, World!

In the verbose output for this HTTP request and all subsequent ones, some of the HTTP response headers have been omitted for brevity.

OK, all set.

Getting started

CORS, or Cross Origin Resource Sharing, “is an HTTP-header based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources”. You come across it in the browser when wanting to consume resources from a different server to the one, the “origin”, that the consuming code came from.

There’s a section on CORS in the Node.js Best Practices part of Capire. In there, it merely says:

“If not running in production, CAP’s default server allows all origins. For production, you can add CORS to your server as follows …”

That tantalisingly short paragraph got me hooked. What does that mean? How does that work? I knew that finding out the answers to these questions would help me with providing what my colleague was asking for.

There are three parts to the paragraph:

“if not running in production””CAP’s default server allows all origins””you can add CORS to your server as follows”

Let’s take the “default server” part first.

Default server support

What is the “default server”? Basically, it’s the process that runs when you invoke something like cds watch, or cds serve, and is also known as the built-in server.js.

So what sort of support are we looking for anyway? CORS support comes in the form of HTTP headers, and the ones that we should be expecting are returned in the HTTP response. The header names all start Access-Control-…, such as Access-Control-Allow-Origin.

But there are no CORS headers in the response to the basic service test above:

< HTTP/1.1 200 OK
< X-Powered-By: Express
< Content-Type: text/plain; charset=utf-8
< Content-Length: 13

That’s because the HTTP request didn’t include any headers in the request that make use of the CORS features. The basics can be triggered by including an Origin HTTP header in the request (this is done automatically by the browser in such cross origin resource retrieval circumstances).

Regular CORS processing

Let’s do that and see what we get from the CAP server. The important thing for this test is to specify a value for the Origin HTTP header that is different to the CAP server. Let’s use qmacro.org:

; curl
–verbose
–header ‘Origin: https://qmacro.org’
–url localhost:4004/rest/corstest/go
> GET /rest/corstest/go HTTP/1.1
> Host: localhost:4004
> User-Agent: curl/7.88.1
> Accept: */*
> Origin: https://qmacro.org
>
< HTTP/1.1 200 OK
< X-Powered-By: Express
< access-control-allow-origin: https://qmacro.org
< Content-Type: text/plain; charset=utf-8
< Content-Length: 13
<
Hello, World!

Check out that extra header in the response, shown in the verbose output:

< access-control-allow-origin: https://qmacro.org

From a CORS perspective, this response header tells the browser to allow that origin to access the resource being returned.

So where is that header coming from? Well, the answer is in the default server. Specifically that’s @Sap/cds/server.js, which has been installed in the node_modules/ directory during the npm install process earlier. The relevant part is here, in a cors getter:

get cors() {
return process.env.NODE_ENV === ‘production’
? null
: (req, res, next) => {
const { origin } = req.headers
if (origin) {
res.set(‘access-control-allow-origin’, origin)
if (req.method === ‘OPTIONS’)
return res.set(
‘access-control-allow-methods’,
‘GET,HEAD,PUT,PATCH,POST,DELETE’
).end()
}
next()
}
}

I took the liberty of reformatting the code for better readability and so it would fit better width-wise in this blog post.

The middle section is what came into play here. If there’s an Origin header in the request, then an Access-Control-Allow-Origin header is sent in the response, with the same value that came in the request (https://qmacro.org) :

access-control-allow-origin: https://qmacro.org

An alternative value would be * but I think I like this reciprocal approach better.

Header names during runtime in the CAP server are lower-cased for consistency and ease of processing.

But what about that bit that starts with the req.method === ‘OPTIONS’ condition, with the Access-Control-Allow-Methods header (as opposed to the Access-Control-Allow-Origin header?

That’s related to another part of CORS processing – “preflight” requests.

Preflight CORS processing

In some cross origin resource retrieval circumstances, a browser will also send a so-called “preflight” request. Basically, if the intended HTTP request to the remote server is not considered a simple request, then a preflight request is made first.

For example, if the method of the intended request is something other than GET, HEAD or POST, or if there are headers that will be supplied that are not “standard”, then a preflight request is made, to check that the remote server is indeed willing to handle such an intended request.

And preflight requests take the form of an HTTP request with the OPTIONS method. Taking one of those cases of a non-simple request, where the method of the request is going to be PUT, for example, then the browser will first send an HTTP request like this (displayed here using curl’s verbose output convention):

> OPTIONS /rest/corstest/go HTTP/1.1
> Host: localhost:4004
> User-Agent: curl/7.88.1
> Accept: */*
> Origin: https://qmacro.org
> Access-Control-Request-Method: PUT

This is the preflight request. Note the Access-Control-Request-Method header with the method of the intended request.

Unless the remote server responds appropriately to such a preflight request, the browser will not allow the actual request to be made. What is an appropriate response here to this preflight request? Something like this:

< HTTP/1.1 200 OK
< X-Powered-By: Express
< access-control-allow-origin: https://qmacro.org
< access-control-allow-methods: GET,PUT

In other words, a response that tells the browser “yes, PUT requests from this origin are allowed”.

And that is exactly what the default server’s CORS handling mechanism is doing in the condition that checks whether the HTTP method is OPTIONS, i.e. if it’s a preflight request. It adds the Access-Control-Allow-Methods header to response to preflight requests, and includes all the “usual suspect” HTTP methods (GET,HEAD,PUT,PATCH,POST,DELETE).

For testing, we can actually construct a preflight request, using curl’s –request option to be able to specify the HTTP method to use, so that we can see a preflight request/response for real. Here goes:

; curl
–verbose
–request OPTIONS
–header ‘Origin: https://qmacro.org’
–url localhost:4004/rest/corstest/go
> OPTIONS /rest/corstest/go HTTP/1.1
> Host: localhost:4004
> User-Agent: curl/7.88.1
> Accept: */*
> Origin: https://qmacro.org
>
< HTTP/1.1 200 OK
< X-Powered-By: Express
< access-control-allow-origin: https://qmacro.org
< access-control-allow-methods: GET,HEAD,PUT,PATCH,POST,DELETE
< Content-Length: 0

Note that I didn’t actually need to specify an Access-Control-Request-Method header in this preflight request; the CORS support in the default CAP server will just supply an equivalent Allow response header covering the main methods.

Great!

The automatic CORS support context

Next, let’s take the “if not running in production” part.

Running anything in production requires more thinking about security, resilience, and so on. And while this default “yes, we’re open!” CORS support we’ve seen so far is very useful at design time when you’re exploring and iterating, it’s probably not what you want in production.

The configuration profile facilities that CAP Node.js offers includes the standard Node.js approach of using the environment variable NODE_ENV to determine in what “mode” the server is running.

Unless explicitly specified, via a configuration profile (–profile production, or the shorthand –production) or simply directly, via the value production set for NODE_ENV4, the CAP server is deemed NOT to be in productive mode.

The startup of the simple CAP server here was brought about simply with cds watch, so it is not running in “production mode” either.

And this is what’s referenced in the first part of the CORS getter in @Sap/cds/server.js that we saw earlier:

get cors() {
return process.env.NODE_ENV === ‘production’
? null
: (req, res, next) => {
…
}
}

Here, through the use of one of my favourite constructs, the ternary operator, the CORS getter will either return the anonymous function (req, res, next) => { … } that adds the CORS “allow” response headers, or nothing at all (null), depending on the value of NODE_ENV.

So when the cors object property is referenced in the running server to potentially provide CORS processing for a request, there will either be a function ready to do that, or, in the case of a production context, nothing to do anything at all.

Adding custom CORS headers

The last of the three parts, “you can add CORS to your server as follows”, is where we move away from the standard CORS facilities of the default server.

The standard facilities will return, as appropriate, one or both of these headers:

Access-Control-Allow-OriginAccess-Control-Allow-Methods

My colleague’s request for CORS support would have normally been fulfilled by this. The method of the remote request being made from his web app origin was GET. This falls into the “simple request” category. But the remote requests will also include a custom header CommunityID.

If you worked through the tasks in last August’s Developer Challenge on APIs, you may remember this header. The hash facility described in Task 0 – Learn to share your task results requires you to supply your SAP Community ID in the form of a header in the HTTP request, like this:

CommunityID: qmacro

This hash facility is the service that my colleague was wanting to call remotely from his web app. And the requirement for this custom header when calling the service5 meant that such requests are not considered “simple”.

This in turn meant that preflight requests would be made. Not only that, but the custom header CommunityID would be supplied in such preflight requests in an Access-Control-Request-Headers header too, in a similar way to how any “unusual” HTTP methods would be supplied in an Access-Control-Request-Method header. And the browser will expect, in the responses to such preflight requests, that the custom header is included in an Access-Control-Allow-Headers header.

But while the built-in CORS handling of the default CAP server provides preflight response support for Access-Control-Request-Method headers, it doesn’t provide support for Access-Control-Request-Headers headers.

We can debate whether this should be standard in the default CAP server, i.e. how much CORS support we should expect out of the box, but here I saw it as an opportunity to learn how I might extend the support myself.

Using a custom server.js

The Boostrapping Servers section of Capire includes information about being able to supply your own custom server logic, like this:

const cds = require(‘@sap/cds’)
// react on bootstrapping events…
cds.on(‘bootstrap’, …)

This is particularly relevant when we revisit that section on CORS mentioned earlier, where it says “… For production, you can add CORS to your server as follows”. And the code example given there is in the context of such a bootstrap event for which custom server implementations are often used – i.e. to hook into part of the CAP server startup to add custom logic:

const ORIGINS = { ‘https://example.com’: 1 }
cds.on(‘bootstrap’, async app => {
app.use((req, res, next) => {
…
})
})

The CORS-relevant code presented in this section is similar to the code in the built-in server (as the point of the example shown is to supply an equivalent level of CORS handling that comes out of the box in non production mode). But what was needed to satisfy my colleague’s requirement was to handle the custom HTTP header information in the CORS preflight requests.

Implementing a custom server.js

Essentially I needed to “flip” the value of any incoming Access-Control-Request-Headers header in preflight HTTP requests, by sending that value back in an Access-Control-Allow-Headers header in each corresponding HTTP response.

How might that look? Well, here’s one approach. Note that this code can be simply stored in a file called server.js which will then be picked up automatically on startup:

const cds = require(‘@sap/cds’)
const log = cds.log(‘custom-cors’, ‘info’)
const ALLOWED = /(.build.cloud.sap|bqmacro.org)$/i

log(‘In custom server.js’)

cds.on(‘bootstrap’, async app => {
app.use((req, res, next) => {

const {
‘access-control-request-headers’: request_headers,
origin
} = req.headers

Breaking this down:

We not only have the cds constant defined, just like in the example code earlier, but also a custom logging constant log. This is so we can emit log output and have it appear in the CAP server output with a prefix we can easily recognise.There’s also an ALLOWED constant which is a regular expression that we can use to check the origin, to determine whether or not we want to perform a “headers flip”. This particular regular expression allows anything ending with .build.cloud.sap, and anything from my own qmacro.org domain6.Following the pattern from the example, we have some logic inside a custom function (req, res, next) => { … } that will receive and get to have a say in processing incoming requests.

The logic inside that custom function goes like this:

Grab the values of any Origin header and any Access-Control-Request-Headers header7If the request method is OPTIONS (signifying a possible preflight request)plus if there’s a value for the Origin headerplus if there’s a value for the Access-Control-Request-Headers headerand the origin is “allowed” according to the regular expressionthen flip the value by adding an Access-Control-Allow-Headers header, with that header value, to the HTTP responsethen “let go” and allow any further processing of that HTTP request to take place

The custom server.js logic in action

Here’s what happens when we try this out. We have the above code in server.js in the CAP project’s root directory. Here’s a simulation of a preflight request that will be made from the browser in the context of my colleague’s web app (except that it’s to the test CAP service here of course):

curl
–verbose
–request OPTIONS
–header ‘Access-Control-Request-Method: GET’
–header ‘Access-Control-Request-Headers: communityid’
–header ‘origin: https://testing-42p9ebmu.eu10.apps.build.cloud.sap’
–url localhost:4004/rest/corstest/go

Here’s the corresponding HTTP request and response details from that verbose output from curl:

> OPTIONS /rest/corstest/go HTTP/1.1
> Host: localhost:4004
> User-Agent: curl/7.88.1
> Accept: */*
> Access-Control-Request-Method: GET
> Access-Control-Request-Headers: communityid
> origin: https://testing-42p9ebmu.preview.eu10.apps.build.cloud.sap
>
< HTTP/1.1 200 OK
< X-Powered-By: Express
< access-control-allow-headers: communityid
< access-control-allow-origin: https://testing-42p9ebmu.eu10.apps.build.cloud.sap
< access-control-allow-methods: GET,HEAD,PUT,PATCH,POST,DELETE
< Content-Length: 0

Excellent – we now have the communityid header value “flipped” and returned in the CORS preflight response.

And here’s (some reduced) log output from the CAP server, showing the loading of the custom server, and the custom log record output too:

[cds] – loading server from { file: ‘server.js’ }
[custom-cors] – in custom server.js
[cds] – loaded model from 1 file(s):

services.cds

…

[cds] – serving corstest { impl: ‘services.js’, path: ‘/rest/corstest’ }

[cds] – server listening on { url: ‘http://localhost:4004’ }
[cds] – launched at 3/31/2024, 8:20:37 AM, version: 7.8.0, in: 2.226s
[cds] – [ terminate with ^C ]

[custom-cors] – Adding allow-headers for communityid

Wrapping up

That’s pretty much mission accomplished, and my colleague can now successfully make use of my service from the web app, served from a different origin, in the browser.

Footnotes

1: This phrase borrows from “the simplest thing that could possibly work”, from Ward Cunningham. See my recording of “The Simplest Thing that Could Possibly Work, A conversation with Ward Cunningham” in the Tech Aloud podcast episode.

2: You may have noticed the removal of the standard directories app/, srv/ and db/ when we set this project up; this is just to keep things as simple as possible. The file name services.cds (and its corresponding default implementation file services.js) is part of the CAP server “roots” that are valid default locations and files that it looks at. You can see this for yourself by running cds env roots which will emit [ ‘db/’, ‘srv/’, ‘app/’, ‘schema’, ‘services’ ].

3: When asked to provide verbose output, curl prefixes the outgoing HTTP request headers with > and the incoming HTTP response headers with <.

4: Ultimately, however you specify the mode, the appropriate value will end up in NODE_ENV for the server to be able to check.

5: The requirement to supply a custom header in calls to the hash facility was deliberate, to encourage the participants to explore a tiny bit beyond standard HTTP requests. After all, the challenge was all about APIs and making HTTP calls.

6: The b is a word boundary assertion, and used here means that it will allow values like https://qmacro.org, http://test.qmacro.org and so on, but not something like fakeqmacro.org.

7: This is done using destructuring, and the first of the two assignments has the slightly extended syntax, to provide the alternative identifier request_headers, as access-control-request-headers would not be a valid JavaScript identifier.

Originally published on qmacro.org

A colleague asked me if I could add CORS support to a service I was running, built with the SAP Cloud Application Programming Model (CAP). CAP already has some basic support for CORS, so I dug in. Here’s what I learned, about CORS headers, preflight requests, CAP custom servers and more.The @sap/approuter has full support for CORS but I wanted to find out about what CAP offers and how to extend it. Specifically, this exploration was made with @sap/cds at version 7.8.0.Test serviceBefore diving in, let’s create the simplest server that could possibly work1 to explore CORS support in CAP. First, a minimal project:# /home/user/work/scratch
; cds init corstest
&& cd $_
&& rm -rf .vscode/ app/ srv/ db/ README.md
&& tree -a
Creating new CAP project in ./corstest

Adding feature ‘nodejs’…

1 directory, 4 filesNow, just the simplest test REST style service. In services.cds2:@protocol: ‘rest’
service corstest {
function go() returns String;
}And in the default implementation file for this service file, i.e. services.js:module.exports = (s) =>
s.on(‘go’, () => `Hello, World!`)Let’s also install the runtime locally with npm install (as we’ll want to look into one of the files there later), and start the server up with cds watch. Now we can perform a basic test, asking for verbose output3, to see what we get:# /home/user/work/scratch/corstest
; curl –verbose –url localhost:4004/rest/corstest/go
> GET /rest/corstest/go HTTP/1.1
> Host: localhost:4004
> User-Agent: curl/7.88.1
> Accept: */*
>
< HTTP/1.1 200 OK
< X-Powered-By: Express
< Content-Type: text/plain; charset=utf-8
< Content-Length: 13
<
Hello, World!In the verbose output for this HTTP request and all subsequent ones, some of the HTTP response headers have been omitted for brevity.OK, all set.Getting startedCORS, or Cross Origin Resource Sharing, “is an HTTP-header based mechanism that allows a server to indicate any origins (domain, scheme, or port) other than its own from which a browser should permit loading resources”. You come across it in the browser when wanting to consume resources from a different server to the one, the “origin”, that the consuming code came from.There’s a section on CORS in the Node.js Best Practices part of Capire. In there, it merely says:”If not running in production, CAP’s default server allows all origins. For production, you can add CORS to your server as follows …”That tantalisingly short paragraph got me hooked. What does that mean? How does that work? I knew that finding out the answers to these questions would help me with providing what my colleague was asking for.There are three parts to the paragraph:”if not running in production””CAP’s default server allows all origins””you can add CORS to your server as follows”Let’s take the “default server” part first.Default server supportWhat is the “default server”? Basically, it’s the process that runs when you invoke something like cds watch, or cds serve, and is also known as the built-in server.js.So what sort of support are we looking for anyway? CORS support comes in the form of HTTP headers, and the ones that we should be expecting are returned in the HTTP response. The header names all start Access-Control-…, such as Access-Control-Allow-Origin.But there are no CORS headers in the response to the basic service test above:< HTTP/1.1 200 OK
< X-Powered-By: Express
< Content-Type: text/plain; charset=utf-8
< Content-Length: 13That’s because the HTTP request didn’t include any headers in the request that make use of the CORS features. The basics can be triggered by including an Origin HTTP header in the request (this is done automatically by the browser in such cross origin resource retrieval circumstances).Regular CORS processingLet’s do that and see what we get from the CAP server. The important thing for this test is to specify a value for the Origin HTTP header that is different to the CAP server. Let’s use qmacro.org:; curl
–verbose
–header ‘Origin: https://qmacro.org’
–url localhost:4004/rest/corstest/go
> GET /rest/corstest/go HTTP/1.1
> Host: localhost:4004
> User-Agent: curl/7.88.1
> Accept: */*
> Origin: https://qmacro.org
>
< HTTP/1.1 200 OK
< X-Powered-By: Express
< access-control-allow-origin: https://qmacro.org
< Content-Type: text/plain; charset=utf-8
< Content-Length: 13
<
Hello, World!Check out that extra header in the response, shown in the verbose output:< access-control-allow-origin: https://qmacro.orgFrom a CORS perspective, this response header tells the browser to allow that origin to access the resource being returned.So where is that header coming from? Well, the answer is in the default server. Specifically that’s @Sap/cds/server.js, which has been installed in the node_modules/ directory during the npm install process earlier. The relevant part is here, in a cors getter:get cors() {
return process.env.NODE_ENV === ‘production’
? null
: (req, res, next) => {
const { origin } = req.headers
if (origin) {
res.set(‘access-control-allow-origin’, origin)
if (req.method === ‘OPTIONS’)
return res.set(
‘access-control-allow-methods’,
‘GET,HEAD,PUT,PATCH,POST,DELETE’
).end()
}
next()
}
}I took the liberty of reformatting the code for better readability and so it would fit better width-wise in this blog post.The middle section is what came into play here. If there’s an Origin header in the request, then an Access-Control-Allow-Origin header is sent in the response, with the same value that came in the request (https://qmacro.org) :access-control-allow-origin: https://qmacro.orgAn alternative value would be * but I think I like this reciprocal approach better.Header names during runtime in the CAP server are lower-cased for consistency and ease of processing.But what about that bit that starts with the req.method === ‘OPTIONS’ condition, with the Access-Control-Allow-Methods header (as opposed to the Access-Control-Allow-Origin header?That’s related to another part of CORS processing – “preflight” requests.Preflight CORS processingIn some cross origin resource retrieval circumstances, a browser will also send a so-called “preflight” request. Basically, if the intended HTTP request to the remote server is not considered a simple request, then a preflight request is made first.For example, if the method of the intended request is something other than GET, HEAD or POST, or if there are headers that will be supplied that are not “standard”, then a preflight request is made, to check that the remote server is indeed willing to handle such an intended request.And preflight requests take the form of an HTTP request with the OPTIONS method. Taking one of those cases of a non-simple request, where the method of the request is going to be PUT, for example, then the browser will first send an HTTP request like this (displayed here using curl’s verbose output convention):> OPTIONS /rest/corstest/go HTTP/1.1
> Host: localhost:4004
> User-Agent: curl/7.88.1
> Accept: */*
> Origin: https://qmacro.org
> Access-Control-Request-Method: PUTThis is the preflight request. Note the Access-Control-Request-Method header with the method of the intended request.Unless the remote server responds appropriately to such a preflight request, the browser will not allow the actual request to be made. What is an appropriate response here to this preflight request? Something like this:< HTTP/1.1 200 OK
< X-Powered-By: Express
< access-control-allow-origin: https://qmacro.org
< access-control-allow-methods: GET,PUTIn other words, a response that tells the browser “yes, PUT requests from this origin are allowed”.And that is exactly what the default server’s CORS handling mechanism is doing in the condition that checks whether the HTTP method is OPTIONS, i.e. if it’s a preflight request. It adds the Access-Control-Allow-Methods header to response to preflight requests, and includes all the “usual suspect” HTTP methods (GET,HEAD,PUT,PATCH,POST,DELETE).For testing, we can actually construct a preflight request, using curl’s –request option to be able to specify the HTTP method to use, so that we can see a preflight request/response for real. Here goes:; curl
–verbose
–request OPTIONS
–header ‘Origin: https://qmacro.org’
–url localhost:4004/rest/corstest/go
> OPTIONS /rest/corstest/go HTTP/1.1
> Host: localhost:4004
> User-Agent: curl/7.88.1
> Accept: */*
> Origin: https://qmacro.org
>
< HTTP/1.1 200 OK
< X-Powered-By: Express
< access-control-allow-origin: https://qmacro.org
< access-control-allow-methods: GET,HEAD,PUT,PATCH,POST,DELETE
< Content-Length: 0Note that I didn’t actually need to specify an Access-Control-Request-Method header in this preflight request; the CORS support in the default CAP server will just supply an equivalent Allow response header covering the main methods.Great!The automatic CORS support contextNext, let’s take the “if not running in production” part.Running anything in production requires more thinking about security, resilience, and so on. And while this default “yes, we’re open!” CORS support we’ve seen so far is very useful at design time when you’re exploring and iterating, it’s probably not what you want in production.The configuration profile facilities that CAP Node.js offers includes the standard Node.js approach of using the environment variable NODE_ENV to determine in what “mode” the server is running.Unless explicitly specified, via a configuration profile (–profile production, or the shorthand –production) or simply directly, via the value production set for NODE_ENV4, the CAP server is deemed NOT to be in productive mode.The startup of the simple CAP server here was brought about simply with cds watch, so it is not running in “production mode” either.And this is what’s referenced in the first part of the CORS getter in @Sap/cds/server.js that we saw earlier:get cors() {
return process.env.NODE_ENV === ‘production’
? null
: (req, res, next) => {
…
}
}Here, through the use of one of my favourite constructs, the ternary operator, the CORS getter will either return the anonymous function (req, res, next) => { … } that adds the CORS “allow” response headers, or nothing at all (null), depending on the value of NODE_ENV.So when the cors object property is referenced in the running server to potentially provide CORS processing for a request, there will either be a function ready to do that, or, in the case of a production context, nothing to do anything at all.Adding custom CORS headersThe last of the three parts, “you can add CORS to your server as follows”, is where we move away from the standard CORS facilities of the default server.The standard facilities will return, as appropriate, one or both of these headers:Access-Control-Allow-OriginAccess-Control-Allow-MethodsMy colleague’s request for CORS support would have normally been fulfilled by this. The method of the remote request being made from his web app origin was GET. This falls into the “simple request” category. But the remote requests will also include a custom header CommunityID.If you worked through the tasks in last August’s Developer Challenge on APIs, you may remember this header. The hash facility described in Task 0 – Learn to share your task results requires you to supply your SAP Community ID in the form of a header in the HTTP request, like this:CommunityID: qmacroThis hash facility is the service that my colleague was wanting to call remotely from his web app. And the requirement for this custom header when calling the service5 meant that such requests are not considered “simple”.This in turn meant that preflight requests would be made. Not only that, but the custom header CommunityID would be supplied in such preflight requests in an Access-Control-Request-Headers header too, in a similar way to how any “unusual” HTTP methods would be supplied in an Access-Control-Request-Method header. And the browser will expect, in the responses to such preflight requests, that the custom header is included in an Access-Control-Allow-Headers header.But while the built-in CORS handling of the default CAP server provides preflight response support for Access-Control-Request-Method headers, it doesn’t provide support for Access-Control-Request-Headers headers.We can debate whether this should be standard in the default CAP server, i.e. how much CORS support we should expect out of the box, but here I saw it as an opportunity to learn how I might extend the support myself.Using a custom server.jsThe Boostrapping Servers section of Capire includes information about being able to supply your own custom server logic, like this:const cds = require(‘@sap/cds’)
// react on bootstrapping events…
cds.on(‘bootstrap’, …)This is particularly relevant when we revisit that section on CORS mentioned earlier, where it says “… For production, you can add CORS to your server as follows”. And the code example given there is in the context of such a bootstrap event for which custom server implementations are often used – i.e. to hook into part of the CAP server startup to add custom logic:const ORIGINS = { ‘https://example.com’: 1 }
cds.on(‘bootstrap’, async app => {
app.use((req, res, next) => {
…
})
})The CORS-relevant code presented in this section is similar to the code in the built-in server (as the point of the example shown is to supply an equivalent level of CORS handling that comes out of the box in non production mode). But what was needed to satisfy my colleague’s requirement was to handle the custom HTTP header information in the CORS preflight requests.Implementing a custom server.jsEssentially I needed to “flip” the value of any incoming Access-Control-Request-Headers header in preflight HTTP requests, by sending that value back in an Access-Control-Allow-Headers header in each corresponding HTTP response.How might that look? Well, here’s one approach. Note that this code can be simply stored in a file called server.js which will then be picked up automatically on startup:const cds = require(‘@sap/cds’)
const log = cds.log(‘custom-cors’, ‘info’)
const ALLOWED = /(.build.cloud.sap|bqmacro.org)$/i

log(‘In custom server.js’)

cds.on(‘bootstrap’, async app => {
app.use((req, res, next) => {

const {
‘access-control-request-headers’: request_headers,
origin
} = req.headers

// Handle headers request in preflight CORS requests
if (
req.method === ‘OPTIONS’
&& origin
&& request_headers
&& ALLOWED.test(origin)
) {
log(`Adding allow-headers for ${request_headers}`)
res.set(
‘access-control-allow-headers’,
request_headers
)
}
next()
})
})Breaking this down:We not only have the cds constant defined, just like in the example code earlier, but also a custom logging constant log. This is so we can emit log output and have it appear in the CAP server output with a prefix we can easily recognise.There’s also an ALLOWED constant which is a regular expression that we can use to check the origin, to determine whether or not we want to perform a “headers flip”. This particular regular expression allows anything ending with .build.cloud.sap, and anything from my own qmacro.org domain6.Following the pattern from the example, we have some logic inside a custom function (req, res, next) => { … } that will receive and get to have a say in processing incoming requests.The logic inside that custom function goes like this:Grab the values of any Origin header and any Access-Control-Request-Headers header7If the request method is OPTIONS (signifying a possible preflight request)plus if there’s a value for the Origin headerplus if there’s a value for the Access-Control-Request-Headers headerand the origin is “allowed” according to the regular expressionthen flip the value by adding an Access-Control-Allow-Headers header, with that header value, to the HTTP responsethen “let go” and allow any further processing of that HTTP request to take placeThe custom server.js logic in actionHere’s what happens when we try this out. We have the above code in server.js in the CAP project’s root directory. Here’s a simulation of a preflight request that will be made from the browser in the context of my colleague’s web app (except that it’s to the test CAP service here of course):curl
–verbose
–request OPTIONS
–header ‘Access-Control-Request-Method: GET’
–header ‘Access-Control-Request-Headers: communityid’
–header ‘origin: https://testing-42p9ebmu.eu10.apps.build.cloud.sap’
–url localhost:4004/rest/corstest/goHere’s the corresponding HTTP request and response details from that verbose output from curl:> OPTIONS /rest/corstest/go HTTP/1.1
> Host: localhost:4004
> User-Agent: curl/7.88.1
> Accept: */*
> Access-Control-Request-Method: GET
> Access-Control-Request-Headers: communityid
> origin: https://testing-42p9ebmu.preview.eu10.apps.build.cloud.sap
>
< HTTP/1.1 200 OK
< X-Powered-By: Express
< access-control-allow-headers: communityid
< access-control-allow-origin: https://testing-42p9ebmu.eu10.apps.build.cloud.sap
< access-control-allow-methods: GET,HEAD,PUT,PATCH,POST,DELETE
< Content-Length: 0Excellent – we now have the communityid header value “flipped” and returned in the CORS preflight response.And here’s (some reduced) log output from the CAP server, showing the loading of the custom server, and the custom log record output too:[cds] – loading server from { file: ‘server.js’ }
[custom-cors] – in custom server.js
[cds] – loaded model from 1 file(s):

services.cds

…

[cds] – serving corstest { impl: ‘services.js’, path: ‘/rest/corstest’ }

[cds] – server listening on { url: ‘http://localhost:4004’ }
[cds] – launched at 3/31/2024, 8:20:37 AM, version: 7.8.0, in: 2.226s
[cds] – [ terminate with ^C ]

[custom-cors] – Adding allow-headers for communityidWrapping upThat’s pretty much mission accomplished, and my colleague can now successfully make use of my service from the web app, served from a different origin, in the browser. Footnotes1: This phrase borrows from “the simplest thing that could possibly work”, from Ward Cunningham. See my recording of “The Simplest Thing that Could Possibly Work, A conversation with Ward Cunningham” in the Tech Aloud podcast episode.2: You may have noticed the removal of the standard directories app/, srv/ and db/ when we set this project up; this is just to keep things as simple as possible. The file name services.cds (and its corresponding default implementation file services.js) is part of the CAP server “roots” that are valid default locations and files that it looks at. You can see this for yourself by running cds env roots which will emit [ ‘db/’, ‘srv/’, ‘app/’, ‘schema’, ‘services’ ].3: When asked to provide verbose output, curl prefixes the outgoing HTTP request headers with > and the incoming HTTP response headers with <.4: Ultimately, however you specify the mode, the appropriate value will end up in NODE_ENV for the server to be able to check.5: The requirement to supply a custom header in calls to the hash facility was deliberate, to encourage the participants to explore a tiny bit beyond standard HTTP requests. After all, the challenge was all about APIs and making HTTP calls.6: The b is a word boundary assertion, and used here means that it will allow values like https://qmacro.org, http://test.qmacro.org and so on, but not something like fakeqmacro.org.7: This is done using destructuring, and the first of the two assignments has the slightly extended syntax, to provide the alternative identifier request_headers, as access-control-request-headers would not be a valid JavaScript identifier.Originally published on qmacro.org Read More Application Development Blog Posts articles

#SAP