Session changes across solution .net Core 2.1
I have a .net core 2.1 solution and in it, it has a wep API project and for the moment a separate MVC front end project using Razor. In both projects startup.cs file I declare services.AddHttpContextAccessor();
From the front end code I set the session to be 1 hour and I can see the value of the HttpContext.Session.Id. So now a call is made to a WebApi Method and I pass an IhttpContextAccessor object, but now when I look at the session.Id on the passed context it doesn't hold the same value as that set by the calling app. Why isn't the context the same?
In my WebApi I have written a custom AuthorisationFiter and it has been placed on one of the api's Methods. I am referencing the context in the following way:
…..
public class AuthorisationFilter : IAuthorizationFilter
{
private readonly IHttpContextAccessor _httpContext;
public AuthorisationFilter(IHttpContextAccessor httpContext) => _httpContext = httpContext;
public void OnAuthorization(AuthorizationFilterContext context)
{…….
c# asp.net-mvc asp.net-web-api
asked Nov 20 '18 at 8:57
bilpor
1,01011128
add a comment |
I have a .net core 2.1 solution and in it, it has a wep API project and for the moment a separate MVC front end project using Razor. In both projects startup.cs file I declare services.AddHttpContextAccessor();
From the front end code I set the session to be 1 hour and I can see the value of the HttpContext.Session.Id. So now a call is made to a WebApi Method and I pass an IhttpContextAccessor object, but now when I look at the session.Id on the passed context it doesn't hold the same value as that set by the calling app. Why isn't the context the same?
In my WebApi I have written a custom AuthorisationFiter and it has been placed on one of the api's Methods. I am referencing the context in the following way:
…..
public class AuthorisationFilter : IAuthorizationFilter
{
private readonly IHttpContextAccessor _httpContext;
public AuthorisationFilter(IHttpContextAccessor httpContext) => _httpContext = httpContext;
public void OnAuthorization(AuthorizationFilterContext context)
{…….
c# asp.net-mvc asp.net-web-api
asked Nov 20 '18 at 8:57
bilpor
1,01011128
add a comment |
I have a .net core 2.1 solution and in it, it has a wep API project and for the moment a separate MVC front end project using Razor. In both projects startup.cs file I declare services.AddHttpContextAccessor();
From the front end code I set the session to be 1 hour and I can see the value of the HttpContext.Session.Id. So now a call is made to a WebApi Method and I pass an IhttpContextAccessor object, but now when I look at the session.Id on the passed context it doesn't hold the same value as that set by the calling app. Why isn't the context the same?
In my WebApi I have written a custom AuthorisationFiter and it has been placed on one of the api's Methods. I am referencing the context in the following way:
…..
public class AuthorisationFilter : IAuthorizationFilter
{
private readonly IHttpContextAccessor _httpContext;
public AuthorisationFilter(IHttpContextAccessor httpContext) => _httpContext = httpContext;
public void OnAuthorization(AuthorizationFilterContext context)
{…….
c# asp.net-mvc asp.net-web-api
asked Nov 20 '18 at 8:57
bilpor
1,01011128
I have a .net core 2.1 solution and in it, it has a wep API project and for the moment a separate MVC front end project using Razor. In both projects startup.cs file I declare services.AddHttpContextAccessor();
From the front end code I set the session to be 1 hour and I can see the value of the HttpContext.Session.Id. So now a call is made to a WebApi Method and I pass an IhttpContextAccessor object, but now when I look at the session.Id on the passed context it doesn't hold the same value as that set by the calling app. Why isn't the context the same?
In my WebApi I have written a custom AuthorisationFiter and it has been placed on one of the api's Methods. I am referencing the context in the following way:
…..
public class AuthorisationFilter : IAuthorizationFilter
{
private readonly IHttpContextAccessor _httpContext;
public AuthorisationFilter(IHttpContextAccessor httpContext) => _httpContext = httpContext;
public void OnAuthorization(AuthorizationFilterContext context)
{…….
c# asp.net-mvc asp.net-web-api
c# asp.net-mvc asp.net-web-api
asked Nov 20 '18 at 8:57
bilpor
1,01011128
asked Nov 20 '18 at 8:57
bilpor
1,01011128
asked Nov 20 '18 at 8:57
bilpor
1,01011128
asked Nov 20 '18 at 8:57
bilpor
1,01011128
asked Nov 20 '18 at 8:57
bilpor
1,01011128
1,01011128
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If you have a separate project for the MVC site then you are in fact creating two separate sites running in their own app pools etc. You cannot share Session State between these two, by default session data is stored in-memory for each app. You might be able to setup a shared session store for this, but this sounds like a hack at best and you probably want to look at what you're trying to achieve as there will more than likely be a better way. Further Reading
I'm not sure exactly how you're 'passing' the IHttpContextAccessor object, but this doesn't seem to be a good idea.
These days when creating an API you really want to be making it stateless, using Session State is the exact opposite of this.
answered Nov 20 '18 at 10:50
matt_lethargic
2,02011225
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%2f53389397%2fsession-changes-across-solution-net-core-2-1%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
If you have a separate project for the MVC site then you are in fact creating two separate sites running in their own app pools etc. You cannot share Session State between these two, by default session data is stored in-memory for each app. You might be able to setup a shared session store for this, but this sounds like a hack at best and you probably want to look at what you're trying to achieve as there will more than likely be a better way. Further Reading
I'm not sure exactly how you're 'passing' the IHttpContextAccessor object, but this doesn't seem to be a good idea.
These days when creating an API you really want to be making it stateless, using Session State is the exact opposite of this.
answered Nov 20 '18 at 10:50
matt_lethargic
2,02011225
add a comment |
If you have a separate project for the MVC site then you are in fact creating two separate sites running in their own app pools etc. You cannot share Session State between these two, by default session data is stored in-memory for each app. You might be able to setup a shared session store for this, but this sounds like a hack at best and you probably want to look at what you're trying to achieve as there will more than likely be a better way. Further Reading
I'm not sure exactly how you're 'passing' the IHttpContextAccessor object, but this doesn't seem to be a good idea.
These days when creating an API you really want to be making it stateless, using Session State is the exact opposite of this.
answered Nov 20 '18 at 10:50
matt_lethargic
2,02011225
add a comment |
If you have a separate project for the MVC site then you are in fact creating two separate sites running in their own app pools etc. You cannot share Session State between these two, by default session data is stored in-memory for each app. You might be able to setup a shared session store for this, but this sounds like a hack at best and you probably want to look at what you're trying to achieve as there will more than likely be a better way. Further Reading
I'm not sure exactly how you're 'passing' the IHttpContextAccessor object, but this doesn't seem to be a good idea.
These days when creating an API you really want to be making it stateless, using Session State is the exact opposite of this.
answered Nov 20 '18 at 10:50
matt_lethargic
2,02011225
If you have a separate project for the MVC site then you are in fact creating two separate sites running in their own app pools etc. You cannot share Session State between these two, by default session data is stored in-memory for each app. You might be able to setup a shared session store for this, but this sounds like a hack at best and you probably want to look at what you're trying to achieve as there will more than likely be a better way. Further Reading
I'm not sure exactly how you're 'passing' the IHttpContextAccessor object, but this doesn't seem to be a good idea.
These days when creating an API you really want to be making it stateless, using Session State is the exact opposite of this.
answered Nov 20 '18 at 10:50
matt_lethargic
2,02011225
answered Nov 20 '18 at 10:50
matt_lethargic
2,02011225
answered Nov 20 '18 at 10:50
matt_lethargic
2,02011225
answered Nov 20 '18 at 10:50
matt_lethargic
2,02011225
2,02011225
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.
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%2f53389397%2fsession-changes-across-solution-net-core-2-1%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
