In the root directory of the project of the package. The json file “dev” : “webpack dev – server – the content – base./- open – the inline – hot — compress – history – API – fallback – config build/webpack dev. Config. Js” add – behind the host 192.168.1.5 (fill in your own IP address). This is because the new version of webpack-dev-server checks the hostname by default for security reasons, and breaks access if the hostname is not in the configuration. You can add the following webpack-dev-server configuration to webpack.base.config.js in the build directory: devServer: {disableHostCheck: true,},
Read More:
- Solution of invalid host header in vue-cli3
- Invalid Host header
- A solution to the default invalid host only mode of CentOS virtual machine in VirtualBox
- ERROR Invalid options in vue.config.js: “plugins“ is not allowed
- Vue agent reports an Error 404 nginx configuration method
- Error message from server: ERROR: invalid page header in block of relation base
- An undetermined call to function ‘shell’: missing ‘. Stop. Problem encountered when using shell command in makefile
- Solution to Error 400. The request has an invalid header name
- gateway Internal Server Error 500 Invalid host: lb://xxxxxx
- Solve the problem of Vue running error( process.env.NODE_ Env = =’production ‘) and error in plugin “gulp shell”“
- error: invalid compressed data to inflate file #14: bad zipfile offset (local header sig):
- In Linux shell script, about the commonly used flag [- EQ, GT..] in test and if judgment
- invalid connection string format, a valid format is host:ip:port
- Common shell (1): shell gets the current time stamp of the system
- Error parsing HTTP request header Note: further occurrences of HTTP header p
- “[warning] failed to retrieve plugin descriptor for caused by Maven security agent settings org.apache.maven . plugins:… “
- ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
- Error reported by nested installation esxi host in vsan environment
- Solve the problem that the header file of “graphics. H” cannot be loaded in vs2015
- Modify the tomcat configuration in docker, causing javaagent to report agent library failed to init instrument