How can set the base path of ASP.NET Core app whilst disabling access from the root path?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I know I can set the base path of my service using app.UsePathBase("/AppPath");
so that my API is available from http://foo.com/AppPath/controller1
but if I do this my API is also available from the root path http://foo.com/controller1
. How do I disable access from the root path?
I also tried to use a route like this app.UseMvc(routes => routes.MapRoute("default", "IRate/{controller}/{action}/{id?}"));
but it has the same problem.
The reason I want to do this is because when it is deployed in production it will be deployed under under an Application prefix (not as the root app) and when I am running the API on local host during debugging I want to simulate the production condictions.
asp.net-core
add a comment |
I know I can set the base path of my service using app.UsePathBase("/AppPath");
so that my API is available from http://foo.com/AppPath/controller1
but if I do this my API is also available from the root path http://foo.com/controller1
. How do I disable access from the root path?
I also tried to use a route like this app.UseMvc(routes => routes.MapRoute("default", "IRate/{controller}/{action}/{id?}"));
but it has the same problem.
The reason I want to do this is because when it is deployed in production it will be deployed under under an Application prefix (not as the root app) and when I am running the API on local host during debugging I want to simulate the production condictions.
asp.net-core
add a comment |
I know I can set the base path of my service using app.UsePathBase("/AppPath");
so that my API is available from http://foo.com/AppPath/controller1
but if I do this my API is also available from the root path http://foo.com/controller1
. How do I disable access from the root path?
I also tried to use a route like this app.UseMvc(routes => routes.MapRoute("default", "IRate/{controller}/{action}/{id?}"));
but it has the same problem.
The reason I want to do this is because when it is deployed in production it will be deployed under under an Application prefix (not as the root app) and when I am running the API on local host during debugging I want to simulate the production condictions.
asp.net-core
I know I can set the base path of my service using app.UsePathBase("/AppPath");
so that my API is available from http://foo.com/AppPath/controller1
but if I do this my API is also available from the root path http://foo.com/controller1
. How do I disable access from the root path?
I also tried to use a route like this app.UseMvc(routes => routes.MapRoute("default", "IRate/{controller}/{action}/{id?}"));
but it has the same problem.
The reason I want to do this is because when it is deployed in production it will be deployed under under an Application prefix (not as the root app) and when I am running the API on local host during debugging I want to simulate the production condictions.
asp.net-core
asp.net-core
asked Nov 22 '18 at 11:26
ShaneShane
93021537
93021537
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
That's by design according to this Github issue.
UsePathBase is primarily about getting those segments out of your way because they're a deployment detail, and if they stayed it would mess up your routing.
Consider the alternative. If it were to disable the root path, how would it do so? A 404 isn't really appropriate, presumably that path is available on a separate instance of your site hosting the root. You could use Map as shown above if you really wanted the 404.
If you want to return a 404 when the root is accessed, you can use a nested mapping, which is described in that issue :
In which case, you probably want something closer to this, with a nested
MapMiddleware
:
public void Configure(IApplicationBuilder app)
{
app.Map("/basepath", mainapp =>
{
mainapp.Map("/ping", map => map.Run(async
ctx => await ctx.Response.WriteAsync("pong")));
mainapp.UseMvc();
});
}
This way you specify mappings, routes, etc only for requests that come under /basepath
. Everything else is discarded and returns a 404.
You'll have to remember to call mainapp
instead of app
for all configuration calls. Otherwise you may end up with script and css URLs that point to the root instead of the custom base path. You can avoid this by extracting the configuration code from Configure(app,env)
into a separate method, eg:
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app.Map("/AppPath", mainapp =>
{
mappedConfigure(mainapp,env);
});
}
private void mappedConfigure(IApplicationBuilder app,IHostingEnvironment env)
{
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler("/Home/Error");
// The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
app.UseHsts();
}
app.UseHttpsRedirection();
app.UseStaticFiles();
app.UseCookiePolicy();
app.UseMvc(routes =>
{
routes.MapRoute(
name: "default",
template: "{controller=Home}/{action=Index}/{id?}");
});
}
Thanks very much, this did the trick. It seems that even if I do not specify a route, a default one is applied, something like "{controller=Home}/{action=Index}/{id?}". Is there a way to remove or override this route?
– Shane
Nov 26 '18 at 1:59
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%2f53429942%2fhow-can-set-the-base-path-of-asp-net-core-app-whilst-disabling-access-from-the-r%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
That's by design according to this Github issue.
UsePathBase is primarily about getting those segments out of your way because they're a deployment detail, and if they stayed it would mess up your routing.
Consider the alternative. If it were to disable the root path, how would it do so? A 404 isn't really appropriate, presumably that path is available on a separate instance of your site hosting the root. You could use Map as shown above if you really wanted the 404.
If you want to return a 404 when the root is accessed, you can use a nested mapping, which is described in that issue :
In which case, you probably want something closer to this, with a nested
MapMiddleware
:
public void Configure(IApplicationBuilder app)
{
app.Map("/basepath", mainapp =>
{
mainapp.Map("/ping", map => map.Run(async
ctx => await ctx.Response.WriteAsync("pong")));
mainapp.UseMvc();
});
}
This way you specify mappings, routes, etc only for requests that come under /basepath
. Everything else is discarded and returns a 404.
You'll have to remember to call mainapp
instead of app
for all configuration calls. Otherwise you may end up with script and css URLs that point to the root instead of the custom base path. You can avoid this by extracting the configuration code from Configure(app,env)
into a separate method, eg:
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app.Map("/AppPath", mainapp =>
{
mappedConfigure(mainapp,env);
});
}
private void mappedConfigure(IApplicationBuilder app,IHostingEnvironment env)
{
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler("/Home/Error");
// The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
app.UseHsts();
}
app.UseHttpsRedirection();
app.UseStaticFiles();
app.UseCookiePolicy();
app.UseMvc(routes =>
{
routes.MapRoute(
name: "default",
template: "{controller=Home}/{action=Index}/{id?}");
});
}
Thanks very much, this did the trick. It seems that even if I do not specify a route, a default one is applied, something like "{controller=Home}/{action=Index}/{id?}". Is there a way to remove or override this route?
– Shane
Nov 26 '18 at 1:59
add a comment |
That's by design according to this Github issue.
UsePathBase is primarily about getting those segments out of your way because they're a deployment detail, and if they stayed it would mess up your routing.
Consider the alternative. If it were to disable the root path, how would it do so? A 404 isn't really appropriate, presumably that path is available on a separate instance of your site hosting the root. You could use Map as shown above if you really wanted the 404.
If you want to return a 404 when the root is accessed, you can use a nested mapping, which is described in that issue :
In which case, you probably want something closer to this, with a nested
MapMiddleware
:
public void Configure(IApplicationBuilder app)
{
app.Map("/basepath", mainapp =>
{
mainapp.Map("/ping", map => map.Run(async
ctx => await ctx.Response.WriteAsync("pong")));
mainapp.UseMvc();
});
}
This way you specify mappings, routes, etc only for requests that come under /basepath
. Everything else is discarded and returns a 404.
You'll have to remember to call mainapp
instead of app
for all configuration calls. Otherwise you may end up with script and css URLs that point to the root instead of the custom base path. You can avoid this by extracting the configuration code from Configure(app,env)
into a separate method, eg:
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app.Map("/AppPath", mainapp =>
{
mappedConfigure(mainapp,env);
});
}
private void mappedConfigure(IApplicationBuilder app,IHostingEnvironment env)
{
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler("/Home/Error");
// The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
app.UseHsts();
}
app.UseHttpsRedirection();
app.UseStaticFiles();
app.UseCookiePolicy();
app.UseMvc(routes =>
{
routes.MapRoute(
name: "default",
template: "{controller=Home}/{action=Index}/{id?}");
});
}
Thanks very much, this did the trick. It seems that even if I do not specify a route, a default one is applied, something like "{controller=Home}/{action=Index}/{id?}". Is there a way to remove or override this route?
– Shane
Nov 26 '18 at 1:59
add a comment |
That's by design according to this Github issue.
UsePathBase is primarily about getting those segments out of your way because they're a deployment detail, and if they stayed it would mess up your routing.
Consider the alternative. If it were to disable the root path, how would it do so? A 404 isn't really appropriate, presumably that path is available on a separate instance of your site hosting the root. You could use Map as shown above if you really wanted the 404.
If you want to return a 404 when the root is accessed, you can use a nested mapping, which is described in that issue :
In which case, you probably want something closer to this, with a nested
MapMiddleware
:
public void Configure(IApplicationBuilder app)
{
app.Map("/basepath", mainapp =>
{
mainapp.Map("/ping", map => map.Run(async
ctx => await ctx.Response.WriteAsync("pong")));
mainapp.UseMvc();
});
}
This way you specify mappings, routes, etc only for requests that come under /basepath
. Everything else is discarded and returns a 404.
You'll have to remember to call mainapp
instead of app
for all configuration calls. Otherwise you may end up with script and css URLs that point to the root instead of the custom base path. You can avoid this by extracting the configuration code from Configure(app,env)
into a separate method, eg:
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app.Map("/AppPath", mainapp =>
{
mappedConfigure(mainapp,env);
});
}
private void mappedConfigure(IApplicationBuilder app,IHostingEnvironment env)
{
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler("/Home/Error");
// The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
app.UseHsts();
}
app.UseHttpsRedirection();
app.UseStaticFiles();
app.UseCookiePolicy();
app.UseMvc(routes =>
{
routes.MapRoute(
name: "default",
template: "{controller=Home}/{action=Index}/{id?}");
});
}
That's by design according to this Github issue.
UsePathBase is primarily about getting those segments out of your way because they're a deployment detail, and if they stayed it would mess up your routing.
Consider the alternative. If it were to disable the root path, how would it do so? A 404 isn't really appropriate, presumably that path is available on a separate instance of your site hosting the root. You could use Map as shown above if you really wanted the 404.
If you want to return a 404 when the root is accessed, you can use a nested mapping, which is described in that issue :
In which case, you probably want something closer to this, with a nested
MapMiddleware
:
public void Configure(IApplicationBuilder app)
{
app.Map("/basepath", mainapp =>
{
mainapp.Map("/ping", map => map.Run(async
ctx => await ctx.Response.WriteAsync("pong")));
mainapp.UseMvc();
});
}
This way you specify mappings, routes, etc only for requests that come under /basepath
. Everything else is discarded and returns a 404.
You'll have to remember to call mainapp
instead of app
for all configuration calls. Otherwise you may end up with script and css URLs that point to the root instead of the custom base path. You can avoid this by extracting the configuration code from Configure(app,env)
into a separate method, eg:
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app.Map("/AppPath", mainapp =>
{
mappedConfigure(mainapp,env);
});
}
private void mappedConfigure(IApplicationBuilder app,IHostingEnvironment env)
{
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler("/Home/Error");
// The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
app.UseHsts();
}
app.UseHttpsRedirection();
app.UseStaticFiles();
app.UseCookiePolicy();
app.UseMvc(routes =>
{
routes.MapRoute(
name: "default",
template: "{controller=Home}/{action=Index}/{id?}");
});
}
edited Nov 22 '18 at 12:02
answered Nov 22 '18 at 11:41
Panagiotis KanavosPanagiotis Kanavos
58.1k483115
58.1k483115
Thanks very much, this did the trick. It seems that even if I do not specify a route, a default one is applied, something like "{controller=Home}/{action=Index}/{id?}". Is there a way to remove or override this route?
– Shane
Nov 26 '18 at 1:59
add a comment |
Thanks very much, this did the trick. It seems that even if I do not specify a route, a default one is applied, something like "{controller=Home}/{action=Index}/{id?}". Is there a way to remove or override this route?
– Shane
Nov 26 '18 at 1:59
Thanks very much, this did the trick. It seems that even if I do not specify a route, a default one is applied, something like "{controller=Home}/{action=Index}/{id?}". Is there a way to remove or override this route?
– Shane
Nov 26 '18 at 1:59
Thanks very much, this did the trick. It seems that even if I do not specify a route, a default one is applied, something like "{controller=Home}/{action=Index}/{id?}". Is there a way to remove or override this route?
– Shane
Nov 26 '18 at 1:59
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%2f53429942%2fhow-can-set-the-base-path-of-asp-net-core-app-whilst-disabling-access-from-the-r%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