You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Essentially, users desire the ability to whitelist certain IP addresses so that colleagues can access their dev server to view their work. However, they'd prefer to not have to specify each individual allowed IP.
"it should be safe to whitelist all IP-addresses-like hosts names by default, which would save people having to whitelist them manually."
The text was updated successfully, but these errors were encountered:
orteth01
changed the title
Whitelist all IP-addresses-like hosts names by default in checkHost
Whitelist all IP-address-like hosts names by default in checkHost
Jun 8, 2017
This patch will allow any requests made using an IP-address to always pass the
checkHost-test.
IP-addresses are not susceptible to a dns-rebind like attack so it would make
sense to not block them to make local-network development possible without
needing to disable the host-checks entirely.
fixeswebpack#931
* Always allow requests with IP-address as host in checkHost()
This patch will allow any requests made using an IP-address to always pass the
checkHost-test.
IP-addresses are not susceptible to a dns-rebind like attack so it would make
sense to not block them to make local-network development possible without
needing to disable the host-checks entirely.
fixes#931
* use 'ip'-module to handle ip-address validation.
As per @shellscape's comment, switch to the
[ip](https://npmjs.com/package/ip)-module to do validation of
ip-address-format.
the problem:
Essentially, users desire the ability to whitelist certain IP addresses so that colleagues can access their dev server to view their work. However, they'd prefer to not have to specify each individual allowed IP.
the solution from @edmorley:
"it should be safe to whitelist all IP-addresses-like hosts names by default, which would save people having to whitelist them manually."
The text was updated successfully, but these errors were encountered: