From 3b23bfaccfd541be2086f0897b922c7f154863eb Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 19 Nov 2025 22:59:57 +0000 Subject: [PATCH 1/4] Initial plan From 26bd26e9debae8a0b345dbc8da7763eb5e44df9b Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 19 Nov 2025 23:02:49 +0000 Subject: [PATCH 2/4] Add Safari compatibility note to localhost-tld.md Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com> --- aspnetcore/test/localhost-tld.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/aspnetcore/test/localhost-tld.md b/aspnetcore/test/localhost-tld.md index fa59e6f797eb..10c30b97886e 100644 --- a/aspnetcore/test/localhost-tld.md +++ b/aspnetcore/test/localhost-tld.md @@ -4,7 +4,7 @@ description: Learn how using localhost as top-level domain can make testing easi monikerRange: '>= aspnetcore-10.0' ms.author: tdykstra ms.custom: -ms.date: 08/26/2025 +ms.date: 11/19/2025 title: Support for the .localhost top-level domain uid: test/localhost-tld --- @@ -23,7 +23,9 @@ ASP.NET Core's built-in HTTP server, Kestrel, correctly treats any `*.localhost` ## Browser compatibility -While web browsers automatically resolve `*.localhost` names to the local loopback address, other apps might treat `*.localhost` names as regular domain names and attempt to resolve them via their corresponding DNS stack. If your DNS configuration doesn't resolve `*.localhost` names to an address, they fail to connect. You can continue to use the regular `localhost` name to address your apps when not in a web browser. +While most modern evergreen browsers automatically resolve `*.localhost` names to the local loopback address, Safari on macOS doesn't support this feature. In Safari, you should use the regular `localhost` name instead of `*.localhost` domain names. + +Other apps might treat `*.localhost` names as regular domain names and attempt to resolve them via their corresponding DNS stack. If your DNS configuration doesn't resolve `*.localhost` names to an address, they fail to connect. You can continue to use the regular `localhost` name to address your apps when not in a web browser. ## HTTPS development certificate From 130f318e8e1363da4ccf3901d836a65253cd06d9 Mon Sep 17 00:00:00 2001 From: Wade Pickett Date: Wed, 19 Nov 2025 15:51:37 -0800 Subject: [PATCH 3/4] Apply suggestions from code review - clarified "client" app. --- aspnetcore/test/localhost-tld.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/test/localhost-tld.md b/aspnetcore/test/localhost-tld.md index 10c30b97886e..a339106725fc 100644 --- a/aspnetcore/test/localhost-tld.md +++ b/aspnetcore/test/localhost-tld.md @@ -25,7 +25,7 @@ ASP.NET Core's built-in HTTP server, Kestrel, correctly treats any `*.localhost` While most modern evergreen browsers automatically resolve `*.localhost` names to the local loopback address, Safari on macOS doesn't support this feature. In Safari, you should use the regular `localhost` name instead of `*.localhost` domain names. -Other apps might treat `*.localhost` names as regular domain names and attempt to resolve them via their corresponding DNS stack. If your DNS configuration doesn't resolve `*.localhost` names to an address, they fail to connect. You can continue to use the regular `localhost` name to address your apps when not in a web browser. +Other client apps might treat `*.localhost` names as regular domain names and attempt to resolve them via their corresponding DNS stack. If your DNS configuration doesn't resolve `*.localhost` names to an address, they fail to connect. You can continue to use the regular `localhost` name to address your apps when not in a web browser. ## HTTPS development certificate From fb7930acd70c1b8e53dd21269a2dd9e3aa4ddba0 Mon Sep 17 00:00:00 2001 From: Wade Pickett Date: Fri, 21 Nov 2025 11:54:10 -0800 Subject: [PATCH 4/4] Update aspnetcore/test/localhost-tld.md Co-authored-by: Tom Dykstra --- aspnetcore/test/localhost-tld.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/test/localhost-tld.md b/aspnetcore/test/localhost-tld.md index a339106725fc..7b01857b3ba5 100644 --- a/aspnetcore/test/localhost-tld.md +++ b/aspnetcore/test/localhost-tld.md @@ -25,7 +25,7 @@ ASP.NET Core's built-in HTTP server, Kestrel, correctly treats any `*.localhost` While most modern evergreen browsers automatically resolve `*.localhost` names to the local loopback address, Safari on macOS doesn't support this feature. In Safari, you should use the regular `localhost` name instead of `*.localhost` domain names. -Other client apps might treat `*.localhost` names as regular domain names and attempt to resolve them via their corresponding DNS stack. If your DNS configuration doesn't resolve `*.localhost` names to an address, they fail to connect. You can continue to use the regular `localhost` name to address your apps when not in a web browser. +Some client apps other than Safari and evergreen web browsers treat `*.localhost` names as regular domain names and attempt to resolve them via their corresponding DNS stack. If your DNS configuration doesn't resolve `*.localhost` names to an address, they fail to connect. You can continue to use the regular `localhost` name to address your apps when not in a web browser. ## HTTPS development certificate