typicode/hotel

.localhost domains isn't working in chrome browser

Open

#272 opened on Jan 30, 2018

View on GitHub
 (8 comments) (5 reactions) (0 assignees)JavaScript (9,939 stars) (474 forks)batch import
help wanted

Description

I've setup local (.localhost) domains in System configuration and Browser configuration that following this rule https://github.com/typicode/hotel/blob/master/docs/README.md. Then, I've restart hotel and reload network and browser configuration.

when i try to run http://hotel.localhost/ in chrome, the browser response is

"This page isn’t working hotel.localhost didn’t send any data. ERR_EMPTY_RESPONSE" screenshot at jan 30 12-04-04

However, when i try to run http://hotel.localhost/ in safari, hotel is working correctly screenshot at jan 30 12-05-58

Also when i run http://localhost:2000/ hotel is working correctly both chrome and safari.

Chrome Version 63.0.3239.132 (Official Build) (64-bit) Safari Version 11.0.1 (13604.3.5) MAC OS High Sierra Version 10.13.1

Contributor guide

Tech stack
javascriptnodejs
Domain
backenddeveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic understanding of DNS and proxy configurationFamiliarity with Chrome's handling of .localhost domains
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the issue comments (8 comments) for any workarounds or root cause analysis. Examine the hotel codebase, particularly the domain resolution and proxy setup (likely in lib/proxy.js or similar). Test with different Chrome versions and flags related to .localhost. Consider if the issue is due to Chrome's DNS over HTTPS or policy changes since 2018.