caddy/caddytest/integration/caddyfile_adapt/ambiguous_site_definition.caddyfiletest

example.com
handle {
	respond "one"
}

example.com
handle {
	respond "two"
}
----------
Caddyfile:6: unrecognized directive: example.com
Did you mean to define a second site? If so, you must use curly braces around each site to separate their configurations.
httpcaddyfile: Validates TLS DNS challenge options (#7099) * httpcaddyfile: Validates TLS DNS challenge options Adds validation to the TLS Caddyfile adapter to ensure that when DNS challenge options (such as propagation_delay or dns_ttl) are specified, a DNS provider is also configured. Adds new integration tests to verify this validation logic, and implements a new mechanism for adapt tests to assert a config adapt error. * Add some more AI-generated tests asserting config errors * Parallel doesn't work here, we use global variables * Windows fix 2025-06-30 19:58:16 -04:00			`example.com`
			`handle {`
			`respond "one"`
			`}`

			`example.com`
			`handle {`
			`respond "two"`
			`}`
			`----------`
			`Caddyfile:6: unrecognized directive: example.com`
			`Did you mean to define a second site? If so, you must use curly braces around each site to separate their configurations.`