Light, fluffy, and always free - The AWS Local Emulator alternative
fix(config): accept any Host header again after the Quarkus 3.39 upgrade (#3222)
Hector Ventura1f4d43c4ccb5
diff --git a/src/main/resources/application.yml b/src/main/resources/application.ymlindex 8dff78629b..029ad308f1 100644--- a/src/main/resources/application.yml+++ b/src/main/resources/application.yml@@ -13,6 +13,19 @@ quarkus:http:port: ${floci.port}host: 0.0.0.0+ # Quarkus 3.38 added a Host-header validation filter (DNS-rebinding protection for a dev server)+ # that it switches on by itself whenever the server is bound to loopback, which Floci does in+ # TLS mode: Quarkus listens on 127.0.0.1:4510/4511 behind the TCP proxy on 4566, and the proxy+ # passes the client's Host header through untouched. The filter is an exact-match set with no+ # wildcard support, and with require-localhost it admits only localhost, 127.0.0.1 and [::1].+ # An emulator has to answer under the names it documents and puts in its certificate+ # (localhost.floci.io, *.localhost.floci.io, *.execute-api.localhost.floci.io,+ # host.docker.internal) and under whatever a compose file calls it (FLOCI_HOSTNAME), none of+ # which an exact-match allow-list can express. Disabling the check restores the behaviour of+ # every release before Quarkus 3.39 and of the non-TLS mode, where Quarkus never enables it;+ # the access boundary of a local emulator is the IAM and signature enforcement configuration.+ host-validation:+ require-localhost: falselimits:max-body-size: ${floci.protocols.max-request-size}Mdatasource: