|
|
You're in the
dotnet web services
group:How to get a WS to create a cookie???
dotnet web services:
on the users PC that made the request. All the code I keep finding is how to get a WS to read a cookie, I need it to create one. The below code doesnt add the cookie to my cache. However if I place this in an non asmx page its fine Any help you offer is apperiated [WebMethod(EnableSession=true)] public string CreateToken(string User, string App, string County) { //Do some stuff .... .... HttpCookie myCookie = new HttpCookie("NameMaster"); myCookie.Domain = "mydomain.com"; myCookie["ID"] = Result.ToString(); myCookie["User"] = User; myCookie["App"] = App; myCookie["County"] = County; myCookie.Expires = DateTime.Now.AddMinutes(30); HttpContext.Current.Response.Cookies.Add(myCookie); //doesnt work -- JP
my apoligies for not clarifying. The code does not error out. I just dont get
the cookie in my cache. -- JP ..NET Software Developer [quoted text, click to view] "Joseph Geretz" wrote:
> Hi JP, > > > HttpContext.Current.Response.Cookies.Add(myCookie); //doesnt work > > What do you mean it doesn't work? Do you get an error, or you're just not > seeing the Cookie on the successive request for the next the Web Service > method? If the latter, you ned to set up your WS Proxy on the client to > handle cookies. We enventually settled on using SOAP header, rather than a > cookie, so I don't have live code to demonstrate this, but if I recall > correctly, you need to code something like > > m_WSProxyClass.CookieContainer = new System.Net.CookieContainer(); > > So that your proxy will now have access to cookies for the purpose of > receiving and sending. > > If this doesn't do it for you, I will see if I can dig up some old code from > when we were using cookies. We did manage to get it to work and so should > you. > > Standard caveat applies: If your Web Services are going to rely on coookies, > you will be limited to HTTP clients. Other clients which don't support the > cookie mechanism won't be able to use your services. > > Hope this helps, > > Joseph Geretz > > "JP" <JP@discussions.microsoft.com> wrote in message > news:7713F4F9-7A6C-43F9-BA6D-39981234BABE@microsoft.com... > >I need to design a WS that will after authenicating the user, create a > >cookie > > on the users PC that made the request. All the code I keep finding is how > > to > > get a WS to read a cookie, I need it to create one. The below code doesnt > > add > > the cookie to my cache. However if I place this in an non asmx page its > > fine > > > > Any help you offer is apperiated > > > > [WebMethod(EnableSession=true)] > > public string CreateToken(string User, string App, string County) > > { > > //Do some stuff > > ... > > ... > > > > HttpCookie myCookie = new HttpCookie("NameMaster"); > > myCookie.Domain = "mydomain.com"; > > myCookie["ID"] = Result.ToString(); > > myCookie["User"] = User; > > myCookie["App"] = App; > > myCookie["County"] = County; > > myCookie.Expires = DateTime.Now.AddMinutes(30); > > HttpContext.Current.Response.Cookies.Add(myCookie); //doesnt work > > -- > > JP > > .NET Software Developer > >
Users (progrmmers) will use this service to create a GUID. This GUID along
with other related information will be stored in a cookie on local machine so that our application can authenicate admin requests using the cookie information. This is why the cookie is only valid for 30 mins per request -- JP ..NET Software Developer [quoted text, click to view] "Joseph Geretz" wrote:
> Hi JP, > > > HttpContext.Current.Response.Cookies.Add(myCookie); //doesnt work > > What do you mean it doesn't work? Do you get an error, or you're just not > seeing the Cookie on the successive request for the next the Web Service > method? If the latter, you ned to set up your WS Proxy on the client to > handle cookies. We enventually settled on using SOAP header, rather than a > cookie, so I don't have live code to demonstrate this, but if I recall > correctly, you need to code something like > > m_WSProxyClass.CookieContainer = new System.Net.CookieContainer(); > > So that your proxy will now have access to cookies for the purpose of > receiving and sending. > > If this doesn't do it for you, I will see if I can dig up some old code from > when we were using cookies. We did manage to get it to work and so should > you. > > Standard caveat applies: If your Web Services are going to rely on coookies, > you will be limited to HTTP clients. Other clients which don't support the > cookie mechanism won't be able to use your services. > > Hope this helps, > > Joseph Geretz > > "JP" <JP@discussions.microsoft.com> wrote in message > news:7713F4F9-7A6C-43F9-BA6D-39981234BABE@microsoft.com... > >I need to design a WS that will after authenicating the user, create a > >cookie > > on the users PC that made the request. All the code I keep finding is how > > to > > get a WS to read a cookie, I need it to create one. The below code doesnt > > add > > the cookie to my cache. However if I place this in an non asmx page its > > fine > > > > Any help you offer is apperiated > > > > [WebMethod(EnableSession=true)] > > public string CreateToken(string User, string App, string County) > > { > > //Do some stuff > > ... > > ... > > > > HttpCookie myCookie = new HttpCookie("NameMaster"); > > myCookie.Domain = "mydomain.com"; > > myCookie["ID"] = Result.ToString(); > > myCookie["User"] = User; > > myCookie["App"] = App; > > myCookie["County"] = County; > > myCookie.Expires = DateTime.Now.AddMinutes(30); > > HttpContext.Current.Response.Cookies.Add(myCookie); //doesnt work > > -- > > JP > > .NET Software Developer > >
Hi JP,
[quoted text, click to view] > HttpContext.Current.Response.Cookies.Add(myCookie); //doesnt work What do you mean it doesn't work? Do you get an error, or you're just not seeing the Cookie on the successive request for the next the Web Service method? If the latter, you ned to set up your WS Proxy on the client to handle cookies. We enventually settled on using SOAP header, rather than a cookie, so I don't have live code to demonstrate this, but if I recall correctly, you need to code something like m_WSProxyClass.CookieContainer = new System.Net.CookieContainer(); So that your proxy will now have access to cookies for the purpose of receiving and sending. If this doesn't do it for you, I will see if I can dig up some old code from when we were using cookies. We did manage to get it to work and so should you. Standard caveat applies: If your Web Services are going to rely on coookies, you will be limited to HTTP clients. Other clients which don't support the cookie mechanism won't be able to use your services. Hope this helps, Joseph Geretz [quoted text, click to view] "JP" <JP@discussions.microsoft.com> wrote in message news:7713F4F9-7A6C-43F9-BA6D-39981234BABE@microsoft.com... >I need to design a WS that will after authenicating the user, create a >cookie > on the users PC that made the request. All the code I keep finding is how > to > get a WS to read a cookie, I need it to create one. The below code doesnt > add > the cookie to my cache. However if I place this in an non asmx page its > fine > > Any help you offer is apperiated > > [WebMethod(EnableSession=true)] > public string CreateToken(string User, string App, string County) > { > //Do some stuff > ... > ... > > HttpCookie myCookie = new HttpCookie("NameMaster"); > myCookie.Domain = "mydomain.com"; > myCookie["ID"] = Result.ToString(); > myCookie["User"] = User; > myCookie["App"] = App; > myCookie["County"] = County; > myCookie.Expires = DateTime.Now.AddMinutes(30); > HttpContext.Current.Response.Cookies.Add(myCookie); //doesnt work > -- > JP > .NET Software Developer
Hi JP,
Have a look at the Cache object. The Cache object is a server side store with much of the same functionality as cookies have. So you can place data in the Cache and it will expire after a certain period of time, just as a cookie does. Instead of using a cookie to shuttle data back and forth, the data remains on the server in the cache, keyed by GUID for example, and you can use a SOAP header to shuttle the GUID back and forth between client and server on each request. Your earlier comment about not seeing the cookie in the cache is consistent with the fact that you haven't created a cookiecontainer on the client to maintain the cookie (see my earlier response). Hoep this helps, - Joseph Geretz - [quoted text, click to view] "JP" <JP@discussions.microsoft.com> wrote in message news:7CBB4FF4-3DF2-4020-880D-D72D8153DD9D@microsoft.com... > Users (progrmmers) will use this service to create a GUID. This GUID along > with other related information will be stored in a cookie on local machine > so > that our application can authenicate admin requests using the cookie > information. This is why the cookie is only valid for 30 mins per request > -- > JP > .NET Software Developer > > > "Joseph Geretz" wrote: > >> Hi JP, >> >> > HttpContext.Current.Response.Cookies.Add(myCookie); //doesnt work >> >> What do you mean it doesn't work? Do you get an error, or you're just not >> seeing the Cookie on the successive request for the next the Web Service >> method? If the latter, you ned to set up your WS Proxy on the client to >> handle cookies. We enventually settled on using SOAP header, rather than >> a >> cookie, so I don't have live code to demonstrate this, but if I recall >> correctly, you need to code something like >> >> m_WSProxyClass.CookieContainer = new System.Net.CookieContainer(); >> >> So that your proxy will now have access to cookies for the purpose of >> receiving and sending. >> >> If this doesn't do it for you, I will see if I can dig up some old code >> from >> when we were using cookies. We did manage to get it to work and so should >> you. >> >> Standard caveat applies: If your Web Services are going to rely on >> coookies, >> you will be limited to HTTP clients. Other clients which don't support >> the >> cookie mechanism won't be able to use your services. >> >> Hope this helps, >> >> Joseph Geretz >> >> "JP" <JP@discussions.microsoft.com> wrote in message >> news:7713F4F9-7A6C-43F9-BA6D-39981234BABE@microsoft.com... >> >I need to design a WS that will after authenicating the user, create a >> >cookie >> > on the users PC that made the request. All the code I keep finding is >> > how >> > to >> > get a WS to read a cookie, I need it to create one. The below code >> > doesnt >> > add >> > the cookie to my cache. However if I place this in an non asmx page its >> > fine >> > >> > Any help you offer is apperiated >> > >> > [WebMethod(EnableSession=true)] >> > public string CreateToken(string User, string App, string County) >> > { >> > //Do some stuff >> > ... >> > ... >> > >> > HttpCookie myCookie = new HttpCookie("NameMaster"); >> > myCookie.Domain = "mydomain.com"; >> > myCookie["ID"] = Result.ToString(); >> > myCookie["User"] = User; >> > myCookie["App"] = App; >> > myCookie["County"] = County; >> > myCookie.Expires = DateTime.Now.AddMinutes(30); >> > HttpContext.Current.Response.Cookies.Add(myCookie); //doesnt work >> > -- >> > JP >> > .NET Software Developer >> >> >>
[quoted text, click to view]
"Joseph Geretz" <jgeretz@nospam.com> wrote in message news:eQyvSFfWHHA.488@TK2MSFTNGP06.phx.gbl... > Hi JP, .... > Standard caveat applies: If your Web Services are going to rely on > coookies, you will be limited to HTTP clients. Other clients which don't > support the cookie mechanism won't be able to use your services. In fact, not all HTTP clients will support cookies. Depending on what you mean to use the cookie for, you might do better with a SOAP header. John
Cookies are created by the client (browser). As such, it wouldn't make any
sense for a web service to attempt to create a cookie because it is one step removed from the correct source for cookies, the web server. Client ---> web page --> a web service See how the service is not the right place for this. The code to create the cookie should be in the page/code that calls the cookie. [quoted text, click to view] "JP" <JP@discussions.microsoft.com> wrote in message news:7713F4F9-7A6C-43F9-BA6D-39981234BABE@microsoft.com... >I need to design a WS that will after authenicating the user, create a >cookie > on the users PC that made the request. All the code I keep finding is how > to > get a WS to read a cookie, I need it to create one. The below code doesnt > add > the cookie to my cache. However if I place this in an non asmx page its > fine > > Any help you offer is apperiated > > [WebMethod(EnableSession=true)] > public string CreateToken(string User, string App, string County) > { > //Do some stuff > ... > ... > > HttpCookie myCookie = new HttpCookie("NameMaster"); > myCookie.Domain = "mydomain.com"; > myCookie["ID"] = Result.ToString(); > myCookie["User"] = User; > myCookie["App"] = App; > myCookie["County"] = County; > myCookie.Expires = DateTime.Now.AddMinutes(30); > HttpContext.Current.Response.Cookies.Add(myCookie); //doesnt work > -- > JP > .NET Software Developer
Correction:
The code to create the [quoted text, click to view] > cookie should be in the page/code that calls the *service*. "Scott M." <s-mar@nospam.nospam> wrote in message news:OrygturWHHA.1180@TK2MSFTNGP05.phx.gbl... > Cookies are created by the client (browser). As such, it wouldn't make > any sense for a web service to attempt to create a cookie because it is > one step removed from the correct source for cookies, the web server. > > Client ---> web page --> a web service > > See how the service is not the right place for this. The code to create > the cookie should be in the page/code that calls the cookie. > > > "JP" <JP@discussions.microsoft.com> wrote in message > news:7713F4F9-7A6C-43F9-BA6D-39981234BABE@microsoft.com... >>I need to design a WS that will after authenicating the user, create a >>cookie >> on the users PC that made the request. All the code I keep finding is how >> to >> get a WS to read a cookie, I need it to create one. The below code doesnt >> add >> the cookie to my cache. However if I place this in an non asmx page its >> fine >> >> Any help you offer is apperiated >> >> [WebMethod(EnableSession=true)] >> public string CreateToken(string User, string App, string County) >> { >> //Do some stuff >> ... >> ... >> >> HttpCookie myCookie = new HttpCookie("NameMaster"); >> myCookie.Domain = "mydomain.com"; >> myCookie["ID"] = Result.ToString(); >> myCookie["User"] = User; >> myCookie["App"] = App; >> myCookie["County"] = County; >> myCookie.Expires = DateTime.Now.AddMinutes(30); >> HttpContext.Current.Response.Cookies.Add(myCookie); //doesnt work >> -- >> JP >> .NET Software Developer > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |