Can not use webpack-dev-server as proxy to https website - ERR_TLS_CERT_ALTNAME_INVALID
I try to use the webpack-dev-server
as a proxy for API requests to the remote test server (in order not to raise a heavy Java server on the local machine). The problem is that the remote server uses only HTTPS. For some reason, it does not accept the certificate from the webpack-dev-server, although it opens correctly from the browser.
My package.json
part:
"webpack": "^3.12.0",
"webpack-dev-server": "^2.11.3"
My webpack.config.json
part:
// -- DEV-SERVER
devServer: {
contentBase: artifact,
// publicPath: path.join(artifact, 'build', '/'),
host: "lk-local.net",
port: 8443,
https: {
key: fs.readFileSync('./src/main/profiles/local/cert/webpack/server.key'),
cert: fs.readFileSync('./src/main/profiles/local/cert/webpack/server.crt'),
ca: fs.readFileSync('./src/main/profiles/local/cert/webpack/cacert.crt'),
},
historyApiFallback: true,
hot: true,
headers: {'Access-Control-Allow-Origin': '*'},
proxy: {
'/client-config': 'https://dev-2.MYSERVER.ru/client-config',
'/client-api/*': 'https://dev-2.MYSERVER.ru/client-api/',
secure: false,
changeOrigin: true
}
}
Webpack-dev-server output:
webpack: Compiled successfully.
[HPM] Error occurred while trying to proxy request /client-api/checkBrowser from lk-local.net:8443 to https://dev-2.MYSERVER.ru/client-api/ (ERR_TLS_CERT_ALTNAME_INVALID) (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while trying to proxy request /client-config from lk-local.net:8443 to https://dev-2.MYSERVER.ru/client-config (ERR_TLS_CERT_ALTNAME_INVALID) (https://nodejs.org/api/errors.html#errors_common_system_errors)
Static opens correctly, requests to the API do not work.
I tried to use a different certificates, and replace https
with the true
. The result is unchanged.
How to solve this problem? Thanks!
webpack proxy certificate webpack-dev-server
add a comment |
I try to use the webpack-dev-server
as a proxy for API requests to the remote test server (in order not to raise a heavy Java server on the local machine). The problem is that the remote server uses only HTTPS. For some reason, it does not accept the certificate from the webpack-dev-server, although it opens correctly from the browser.
My package.json
part:
"webpack": "^3.12.0",
"webpack-dev-server": "^2.11.3"
My webpack.config.json
part:
// -- DEV-SERVER
devServer: {
contentBase: artifact,
// publicPath: path.join(artifact, 'build', '/'),
host: "lk-local.net",
port: 8443,
https: {
key: fs.readFileSync('./src/main/profiles/local/cert/webpack/server.key'),
cert: fs.readFileSync('./src/main/profiles/local/cert/webpack/server.crt'),
ca: fs.readFileSync('./src/main/profiles/local/cert/webpack/cacert.crt'),
},
historyApiFallback: true,
hot: true,
headers: {'Access-Control-Allow-Origin': '*'},
proxy: {
'/client-config': 'https://dev-2.MYSERVER.ru/client-config',
'/client-api/*': 'https://dev-2.MYSERVER.ru/client-api/',
secure: false,
changeOrigin: true
}
}
Webpack-dev-server output:
webpack: Compiled successfully.
[HPM] Error occurred while trying to proxy request /client-api/checkBrowser from lk-local.net:8443 to https://dev-2.MYSERVER.ru/client-api/ (ERR_TLS_CERT_ALTNAME_INVALID) (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while trying to proxy request /client-config from lk-local.net:8443 to https://dev-2.MYSERVER.ru/client-config (ERR_TLS_CERT_ALTNAME_INVALID) (https://nodejs.org/api/errors.html#errors_common_system_errors)
Static opens correctly, requests to the API do not work.
I tried to use a different certificates, and replace https
with the true
. The result is unchanged.
How to solve this problem? Thanks!
webpack proxy certificate webpack-dev-server
add a comment |
I try to use the webpack-dev-server
as a proxy for API requests to the remote test server (in order not to raise a heavy Java server on the local machine). The problem is that the remote server uses only HTTPS. For some reason, it does not accept the certificate from the webpack-dev-server, although it opens correctly from the browser.
My package.json
part:
"webpack": "^3.12.0",
"webpack-dev-server": "^2.11.3"
My webpack.config.json
part:
// -- DEV-SERVER
devServer: {
contentBase: artifact,
// publicPath: path.join(artifact, 'build', '/'),
host: "lk-local.net",
port: 8443,
https: {
key: fs.readFileSync('./src/main/profiles/local/cert/webpack/server.key'),
cert: fs.readFileSync('./src/main/profiles/local/cert/webpack/server.crt'),
ca: fs.readFileSync('./src/main/profiles/local/cert/webpack/cacert.crt'),
},
historyApiFallback: true,
hot: true,
headers: {'Access-Control-Allow-Origin': '*'},
proxy: {
'/client-config': 'https://dev-2.MYSERVER.ru/client-config',
'/client-api/*': 'https://dev-2.MYSERVER.ru/client-api/',
secure: false,
changeOrigin: true
}
}
Webpack-dev-server output:
webpack: Compiled successfully.
[HPM] Error occurred while trying to proxy request /client-api/checkBrowser from lk-local.net:8443 to https://dev-2.MYSERVER.ru/client-api/ (ERR_TLS_CERT_ALTNAME_INVALID) (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while trying to proxy request /client-config from lk-local.net:8443 to https://dev-2.MYSERVER.ru/client-config (ERR_TLS_CERT_ALTNAME_INVALID) (https://nodejs.org/api/errors.html#errors_common_system_errors)
Static opens correctly, requests to the API do not work.
I tried to use a different certificates, and replace https
with the true
. The result is unchanged.
How to solve this problem? Thanks!
webpack proxy certificate webpack-dev-server
I try to use the webpack-dev-server
as a proxy for API requests to the remote test server (in order not to raise a heavy Java server on the local machine). The problem is that the remote server uses only HTTPS. For some reason, it does not accept the certificate from the webpack-dev-server, although it opens correctly from the browser.
My package.json
part:
"webpack": "^3.12.0",
"webpack-dev-server": "^2.11.3"
My webpack.config.json
part:
// -- DEV-SERVER
devServer: {
contentBase: artifact,
// publicPath: path.join(artifact, 'build', '/'),
host: "lk-local.net",
port: 8443,
https: {
key: fs.readFileSync('./src/main/profiles/local/cert/webpack/server.key'),
cert: fs.readFileSync('./src/main/profiles/local/cert/webpack/server.crt'),
ca: fs.readFileSync('./src/main/profiles/local/cert/webpack/cacert.crt'),
},
historyApiFallback: true,
hot: true,
headers: {'Access-Control-Allow-Origin': '*'},
proxy: {
'/client-config': 'https://dev-2.MYSERVER.ru/client-config',
'/client-api/*': 'https://dev-2.MYSERVER.ru/client-api/',
secure: false,
changeOrigin: true
}
}
Webpack-dev-server output:
webpack: Compiled successfully.
[HPM] Error occurred while trying to proxy request /client-api/checkBrowser from lk-local.net:8443 to https://dev-2.MYSERVER.ru/client-api/ (ERR_TLS_CERT_ALTNAME_INVALID) (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while trying to proxy request /client-config from lk-local.net:8443 to https://dev-2.MYSERVER.ru/client-config (ERR_TLS_CERT_ALTNAME_INVALID) (https://nodejs.org/api/errors.html#errors_common_system_errors)
Static opens correctly, requests to the API do not work.
I tried to use a different certificates, and replace https
with the true
. The result is unchanged.
How to solve this problem? Thanks!
webpack proxy certificate webpack-dev-server
webpack proxy certificate webpack-dev-server
asked Nov 19 '18 at 6:15
Евгений КарповЕвгений Карпов
1275
1275
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I believe your changeOrigin
and secure
options aren't specified in the right way. The '/client-config': 'https://dev-2.MYSERVER.ru/client-config'
form doesn't support them if I'm reading the docs properly. You can do either:
proxy: {
'/client-config': {
target: 'https://dev-2.MYSERVER.ru/client-config',
secure: false,
changeOrigin: true
},
...
}
or
proxy: [{
context: ['/client-config', '/client-api/*'],
target: 'https://dev-2.MYSERVER.ru/',
secure: false,
changeOrigin: true
}]
btw, if your browser doesn't give the security warnings, you shouldn't need the secure: false
bit, and much better to leave it out.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53369228%2fcan-not-use-webpack-dev-server-as-proxy-to-https-website-err-tls-cert-altname%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I believe your changeOrigin
and secure
options aren't specified in the right way. The '/client-config': 'https://dev-2.MYSERVER.ru/client-config'
form doesn't support them if I'm reading the docs properly. You can do either:
proxy: {
'/client-config': {
target: 'https://dev-2.MYSERVER.ru/client-config',
secure: false,
changeOrigin: true
},
...
}
or
proxy: [{
context: ['/client-config', '/client-api/*'],
target: 'https://dev-2.MYSERVER.ru/',
secure: false,
changeOrigin: true
}]
btw, if your browser doesn't give the security warnings, you shouldn't need the secure: false
bit, and much better to leave it out.
add a comment |
I believe your changeOrigin
and secure
options aren't specified in the right way. The '/client-config': 'https://dev-2.MYSERVER.ru/client-config'
form doesn't support them if I'm reading the docs properly. You can do either:
proxy: {
'/client-config': {
target: 'https://dev-2.MYSERVER.ru/client-config',
secure: false,
changeOrigin: true
},
...
}
or
proxy: [{
context: ['/client-config', '/client-api/*'],
target: 'https://dev-2.MYSERVER.ru/',
secure: false,
changeOrigin: true
}]
btw, if your browser doesn't give the security warnings, you shouldn't need the secure: false
bit, and much better to leave it out.
add a comment |
I believe your changeOrigin
and secure
options aren't specified in the right way. The '/client-config': 'https://dev-2.MYSERVER.ru/client-config'
form doesn't support them if I'm reading the docs properly. You can do either:
proxy: {
'/client-config': {
target: 'https://dev-2.MYSERVER.ru/client-config',
secure: false,
changeOrigin: true
},
...
}
or
proxy: [{
context: ['/client-config', '/client-api/*'],
target: 'https://dev-2.MYSERVER.ru/',
secure: false,
changeOrigin: true
}]
btw, if your browser doesn't give the security warnings, you shouldn't need the secure: false
bit, and much better to leave it out.
I believe your changeOrigin
and secure
options aren't specified in the right way. The '/client-config': 'https://dev-2.MYSERVER.ru/client-config'
form doesn't support them if I'm reading the docs properly. You can do either:
proxy: {
'/client-config': {
target: 'https://dev-2.MYSERVER.ru/client-config',
secure: false,
changeOrigin: true
},
...
}
or
proxy: [{
context: ['/client-config', '/client-api/*'],
target: 'https://dev-2.MYSERVER.ru/',
secure: false,
changeOrigin: true
}]
btw, if your browser doesn't give the security warnings, you shouldn't need the secure: false
bit, and much better to leave it out.
answered Dec 2 '18 at 7:07
Scott LambScott Lamb
1,4121115
1,4121115
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53369228%2fcan-not-use-webpack-dev-server-as-proxy-to-https-website-err-tls-cert-altname%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown