I've created an HttpModule with this guidance to simulate the way Siteminder writes server variables. I can use this method to send Server Variables to other pages on the same site, but when I redirect or post to another website, I'm seeing that my variables
are dropped. Is there a way to ensure that my custom server variables persist?
I have a feeling that IIS may be playing a role here, but not sure how to confirm or work around.
AFAIK ServerVariables are just handled and kept on the web server (even if some variables are a *copy* of http headers taken from the incoming request). For now it seems you would need first to make sure about what the other web site needs exactly (more
likely a http header or a cookie ?)
Thank you for the response. I will look into the cookie part of things. The other website expects a certain http_variable, even if I try to add a header variable with that name it looks like it's being dropped as well. With Google Chrome I can see the header
variable on the outgoing response, but not on the incoming request of the second site.
Maybe there is some correlation with a cookie that I'm missing.
What is the exact expected variable name? To me server variables are just a way for a web server to expose some values easily to each step of the request processing and it is a mix of incoming headers and cookies as well as local server values (such as the
web server version etc...). So in short server variables are AFAIK not part of any http query (some are taken *from* the incoming http query).
Don't you have some kind of integration guide for the product that requires this "server variable" (that likely comes from a header or cookie or maybe they have a module on their side that expose a foprm field or whatever else being part of an http query).
None
0 Points
2 Posts
Adding ServerVariables
Feb 23, 2016 07:45 PM|Cory B|LINK
Referencing this post:
http://forums.asp.net/t/1125149.aspx?Adding+servervariables
I've created an HttpModule with this guidance to simulate the way Siteminder writes server variables. I can use this method to send Server Variables to other pages on the same site, but when I redirect or post to another website, I'm seeing that my variables are dropped. Is there a way to ensure that my custom server variables persist?
I have a feeling that IIS may be playing a role here, but not sure how to confirm or work around.
We're using ASP.NET 4.0 and IIS 7.
Any advice would be helpful!
-Cory
All-Star
44850 Points
16011 Posts
Re: Adding ServerVariables
Feb 23, 2016 08:34 PM|PatriceSc|LINK
Hi,
AFAIK ServerVariables are just handled and kept on the web server (even if some variables are a *copy* of http headers taken from the incoming request). For now it seems you would need first to make sure about what the other web site needs exactly (more likely a http header or a cookie ?)
None
0 Points
2 Posts
Re: Adding ServerVariables
Feb 25, 2016 08:01 PM|Cory B|LINK
Thank you for the response. I will look into the cookie part of things. The other website expects a certain http_variable, even if I try to add a header variable with that name it looks like it's being dropped as well. With Google Chrome I can see the header variable on the outgoing response, but not on the incoming request of the second site.
Maybe there is some correlation with a cookie that I'm missing.
Thanks!
All-Star
44850 Points
16011 Posts
Re: Adding ServerVariables
Feb 25, 2016 08:15 PM|PatriceSc|LINK
What is the exact expected variable name? To me server variables are just a way for a web server to expose some values easily to each step of the request processing and it is a mix of incoming headers and cookies as well as local server values (such as the web server version etc...). So in short server variables are AFAIK not part of any http query (some are taken *from* the incoming http query).
Don't you have some kind of integration guide for the product that requires this "server variable" (that likely comes from a header or cookie or maybe they have a module on their side that expose a foprm field or whatever else being part of an http query).