Are we able to use the X-Authorization header in HTTP endpoints?

[pbiggar]

A user says:

I haven't run into any trouble, I just haven't had much time lately to play around with my canvas.

I did however, "ship" what I have so far. It's a very simple offline-capable SPA at the moment, so there's not a whole lot of Dark-specific functionality to it, yet. At the time, I wasn't sure how to upload static assets to Dark, so its sitting on Netlify right now. My next step is move those assets to Dark. I do see the docs on static assets and they seem straightforward, so I don't anticipate any problems.

Though I do remember one question I had put in slack that I don't believe got answered: Are we able to use the X-Authorization header in HTTP endpoints? That header seems to always get set to "dummy-token" for my requests.

Example:
When I request http POST https://_______.builtwithdark.com/test) "x-authorization:custom" "x-other-header:works" content="hello world", I get:
X-Other-Header: works
X-Authorization: dummy-token
body: {
content: "hello world"
}

Other than that, everything's working great!