localhost:6101 - this is .net core application with angular files in it
When i use first Caddyfile - requests doesn’t proxy to localhost:6101 at all, i get 200 with every request.
When i use second Caddyfile - requests works allright.
If you specify a path in a site address, it’s a path matcher and only matches requests to those domains.
So if you make a request to http://cloud.com/ then it will work. But if you make a request to http://cloud.com/foo.html, then it won’t match because / != /foo.html.
To match all paths, omit the matcher entirely (omit the /), or specify a specific path or path prefix you want to match, like /foo/* etc.
This syntax is useful if you have multiple sites served in sub-paths.
Before we do that though, can we try documenting this better first? I still think it makes sense but people just aren’t aware of it. That’s my bad. I can work on those docs.
(Clearly the deprecation warning isn’t being noticed either – so while an error would force them to recognize it, I still feel like it has some utility…)