Sinatra 4.1 ships with a breaking change that [enables host allowlisting
middleware][1] in local development, which in turn breaks running Search
API through GOV.UK Docker.

This adds an explicit `permitted_hosts` setting for the middleware,
which includes the `search-api.dev.gov.uk` host used by GOV.UK Docker.

[1]: sinatra/sinatra#2053

Per [this](sinatra/sinatra#2053) change, "Defaults to .localhost, .test and any IP address in development mode."

We want our fake server to be able to respond to any request, hence we allow all hosts.

Sinatra 4.1 ships with a breaking change that [enables host allowlisting
middleware][1] in local development, which in turn breaks running Search
API through GOV.UK Docker.

This adds an explicit `permitted_hosts` setting for the middleware in
the development environment, which allows access with arbitrary host
headers.

[1]: sinatra/sinatra#2053

While working on this sinatra/sinatra#2053 in
our project. I noticed than when using Webmock, sinatra logs and
especially the enforced rack-protection were showing this kind of logs:

```
D, [2024-11-22T13:05:16.798156 #26673] DEBUG -- : Rack::Protection::HostAuthorization @all_permitted_hosts=[".company.com"] @permitted_hosts=["company.com"] @domain_hosts=[/\A(?-mix:[a-z0-9\-.]+)company\.com\z/i] @ip_hosts=[] origin_host="" forwarded_host=nil
```

As you can see, `origin_host` is empty, because the header is missing.

When not using webmock, we fallback on `net/http` host header setup.
https://github.com/ruby/net-http/blob/cfbbb50c931a78fc2b5c731b9abeda161e1dfdd1/lib/net/http.rb#L2482

While working on this sinatra/sinatra#2053 in
our project. I noticed than when using Webmock, sinatra logs and
especially the enforced rack-protection were showing this kind of logs:

```
D, [2024-11-22T13:05:16.798156 #26673] DEBUG -- : Rack::Protection::HostAuthorization @all_permitted_hosts=[".company.com"] @permitted_hosts=["company.com"] @domain_hosts=[/\A(?-mix:[a-z0-9\-.]+)company\.com\z/i] @ip_hosts=[] origin_host="" forwarded_host=nil
```

As you can see, `origin_host` is empty, because the header is missing.

When not using webmock, we fallback on `net/http` host header setup.
https://github.com/ruby/net-http/blob/cfbbb50c931a78fc2b5c731b9abeda161e1dfdd1/lib/net/http.rb#L2482

While working on this sinatra/sinatra#2053 in
our project. I noticed than when using Webmock, sinatra logs and
especially the enforced rack-protection were showing this kind of logs:

```
D, [2024-11-22T13:05:16.798156 #26673] DEBUG -- : Rack::Protection::HostAuthorization @all_permitted_hosts=[".company.com"] @permitted_hosts=["company.com"] @domain_hosts=[/\A(?-mix:[a-z0-9\-.]+)company\.com\z/i] @ip_hosts=[] origin_host="" forwarded_host=nil
```

As you can see, `origin_host` is empty, because the header is missing.

When not using webmock, we fallback on `net/http` host header setup.
https://github.com/ruby/net-http/blob/cfbbb50c931a78fc2b5c731b9abeda161e1dfdd1/lib/net/http.rb#L2482

affects sinatra users 4.1.x post sinatra/sinatra#2053

affects sinatra users 4.1.x post sinatra/sinatra#2053

## Which problem is this PR solving?

- [Sinatra 4.1.0 introduced a host authorization option to Sinatra
apps](sinatra/sinatra#2053). That authorization
check was failing requests made in tests.

## Short description of the changes

-  Update the Honeycomb test server stub to allow anybody to talk to it.

Co-authored-by: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>

## Which problem is this PR solving?

- [Sinatra 4.1.0 introduced a host authorization option to Sinatra apps](sinatra/sinatra#2053). That authorization check was failing requests made in tests.

## Short description of the changes

-  Update the test Sinatra server to allow anybody to talk to it.

Co-authored-by: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>

## Which problem is this PR solving?

- [Sinatra 4.1.0 introduced a host authorization option to Sinatra
apps](sinatra/sinatra#2053). That authorization
check was failing requests made in tests.

## Short description of the changes

-  Update the test Sinatra server to allow anybody to talk to it.

---------

Co-authored-by: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com>

….1.0

The acceptance tests failed because Sinatra 4.1.0 introduced `HostAuthorization` sinatra/sinatra#2053, which rejects connections from remote hosts by default unless explicitly allowed. This behavior affects environments where the app is accessed from remote addresses during tests.

Setting `APP_ENV` to `production` fixes that, allowing the tests to pass without further configuration. Updated the environment setup to include this fix.

….10 (#165)

* Fix acceptance test failures caused by HostAuthorization in Sinatra 4.1.0

The acceptance tests failed because Sinatra 4.1.0 introduced `HostAuthorization` sinatra/sinatra#2053, which rejects connections from remote hosts by default unless explicitly allowed. This behavior affects environments where the app is accessed from remote addresses during tests.

Setting `APP_ENV` to `production` fixes that, allowing the tests to pass without further configuration. Updated the environment setup to include this fix.

* Replace docker-compose with docker compose

Updated to use `docker compose`, the newer and recommended way of managing multi-container Docker applications, replacing the deprecated `docker-compose` command.

HostAuthorization was introduced in sinatra/sinatra#2053

HostAuthorization was introduced in sinatra/sinatra#2053