Serve static always add req.url
I'm using serve-static in ExpressJs in nodeJS,
but I have a problem.
I know it's a function and not a bug, but I don't want to add req.url to my root directory.
When I write:
var serve = serveStatic('rootDirectory', {index: 'index.html'})
and when I request, for example, 'http://localhost/test'
It serves rootDirectory/test, instead of 'rootDirectory/'.
How can I prevent from that?
node.js express
add a comment |
I'm using serve-static in ExpressJs in nodeJS,
but I have a problem.
I know it's a function and not a bug, but I don't want to add req.url to my root directory.
When I write:
var serve = serveStatic('rootDirectory', {index: 'index.html'})
and when I request, for example, 'http://localhost/test'
It serves rootDirectory/test, instead of 'rootDirectory/'.
How can I prevent from that?
node.js express
add a comment |
I'm using serve-static in ExpressJs in nodeJS,
but I have a problem.
I know it's a function and not a bug, but I don't want to add req.url to my root directory.
When I write:
var serve = serveStatic('rootDirectory', {index: 'index.html'})
and when I request, for example, 'http://localhost/test'
It serves rootDirectory/test, instead of 'rootDirectory/'.
How can I prevent from that?
node.js express
I'm using serve-static in ExpressJs in nodeJS,
but I have a problem.
I know it's a function and not a bug, but I don't want to add req.url to my root directory.
When I write:
var serve = serveStatic('rootDirectory', {index: 'index.html'})
and when I request, for example, 'http://localhost/test'
It serves rootDirectory/test, instead of 'rootDirectory/'.
How can I prevent from that?
node.js express
node.js express
edited Nov 25 at 11:59
Neil Lunn
97k22170181
97k22170181
asked Nov 22 at 18:22
LightGolgot
142
142
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Ok, I've searched for many things, and I think the absolute solution is to make it by myself with 'fs'. Thanks anyway
1
Instead of adding "closed" to the question's title, you should accept your answer. That way it's easier for others to see that the issue is solved.
– SurvivalMachine
Nov 22 at 18:49
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%2f53436417%2fserve-static-always-add-req-url%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
Ok, I've searched for many things, and I think the absolute solution is to make it by myself with 'fs'. Thanks anyway
1
Instead of adding "closed" to the question's title, you should accept your answer. That way it's easier for others to see that the issue is solved.
– SurvivalMachine
Nov 22 at 18:49
add a comment |
Ok, I've searched for many things, and I think the absolute solution is to make it by myself with 'fs'. Thanks anyway
1
Instead of adding "closed" to the question's title, you should accept your answer. That way it's easier for others to see that the issue is solved.
– SurvivalMachine
Nov 22 at 18:49
add a comment |
Ok, I've searched for many things, and I think the absolute solution is to make it by myself with 'fs'. Thanks anyway
Ok, I've searched for many things, and I think the absolute solution is to make it by myself with 'fs'. Thanks anyway
answered Nov 22 at 18:43
LightGolgot
142
142
1
Instead of adding "closed" to the question's title, you should accept your answer. That way it's easier for others to see that the issue is solved.
– SurvivalMachine
Nov 22 at 18:49
add a comment |
1
Instead of adding "closed" to the question's title, you should accept your answer. That way it's easier for others to see that the issue is solved.
– SurvivalMachine
Nov 22 at 18:49
1
1
Instead of adding "closed" to the question's title, you should accept your answer. That way it's easier for others to see that the issue is solved.
– SurvivalMachine
Nov 22 at 18:49
Instead of adding "closed" to the question's title, you should accept your answer. That way it's easier for others to see that the issue is solved.
– SurvivalMachine
Nov 22 at 18:49
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53436417%2fserve-static-always-add-req-url%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