Every now and then when I’m working using the local development server via retype start, I get a HTTP 403 error. This really confused me for a while, until I spotted the following HTTP header in Chrome inspector: Server: AirTunes/750.14.1.
Apparently macOS now uses this port for AirPlay, so it’s sometimes available and sometimes not. What’s slightly odd is that if I stop and restart retype, it doesn’t detect that the port is already in use by something else.
I would suggest that fixing the port detection would be enough to solve this (so that stopping and restarting uses a different port number), but it might be better to change the default port - at least on macOS - because it may work initially, and then AirPlay will step in and steal the port at random.
Hi,
Every now and then when I’m working using the local development server via
retype start
, I get a HTTP 403 error. This really confused me for a while, until I spotted the following HTTP header in Chrome inspector:Server: AirTunes/750.14.1
.Apparently macOS now uses this port for AirPlay, so it’s sometimes available and sometimes not. What’s slightly odd is that if I stop and restart retype, it doesn’t detect that the port is already in use by something else.
I would suggest that fixing the port detection would be enough to solve this (so that stopping and restarting uses a different port number), but it might be better to change the default port - at least on macOS - because it may work initially, and then AirPlay will step in and steal the port at random.