caddy | A plugin the Caddy web server to act as a backend

ASSUMING the two files have the same number of lines, this will do it:

There are a few options to achieve your goal:

• Basic auth

The simplest solution to secure your services would be Basic Auth, which basically tells your user's browser to ask for a username and password which is then sent to the server.

https://caddyserver.com/docs/caddyfile/directives/basicauth

Even though it is very quick to set up, you lose benefits such as fine-grined access control and your users' ability to change their username/password.

• OAuth

OAuth allows your users to sign in with their own account, for example from Google or Facebook. Take a look at this complete Caddy Auth System: https://github.com/greenpau/caddy-auth-portal

• JWT - Build your own

Finally, if you want to use this challenge as a learning opportunity, you can take a look at JWT based authentication. Take a look at this module: https://github.com/greenpau/caddy-auth-jwt

This would enable you to issue JWT tokens in your node.js application which are then verified by Caddy.

Obviously, all of these solutions do require some research and skill and I would rate their difficulty to implement in ascending order, with your plan of building your own Auth system being the most difficult.

You're using the wrong command. docker-compose run is similiar to docker exec. You want docker-compose -f app.compose.yml up -d to run it in the background or docker-compose -f app.compose.yml up to run it in the foreground (similiar to -ti in docker run)

maybe you can try using

I ended up using a semi-temporary solution, namely:

https://github.com/robbertkl/docker-ipv6nat

which makes configuring IPv6 in docker much simpler. However, a similar feature is expected to come do Docker soon anyway, as tracked by:

• https://github.com/robbertkl/docker-ipv6nat/issues/65
• https://github.com/moby/libnetwork/pull/2572

So this should be the preferred solution for any future users.

As stated on wikipedia, the general format of the X-Forwarded-For is:

Caddy 2 doesn't support neither TLS 1.1 nor TLS 1.0. The minimum version is TLS 1.2 as you can see in the documentation in TLS directive which states

protocols: specifies the minimum and maximum protocol versions. Default min: tls1.2. Default max: tls1.3

In tls: Remove support for TLS 1.0 and TLS 1.1 you can see the commit where they were removed during the development of Caddy 2.

I managed to solve my problem:
The headers were correctly set up by express, and I was getting them when making requests with curl or Postman without changing anything in Caddy.

The problem ended up being that I was making requests to http, Caddy was redirecting these to https, which is no problem for GET requests sent from Postman, but Preflight-requests (OPTIONS) do not support redirects, and because Caddy was making the redirection, it was not reaching express (and CORS setup), throwing the error.

Finally, the solution was simply making my requests to https://my-nice-server.com

Caddy serves http traffic only if you prefix the domain with http scheme.

Here is the modified Caddyfile: