I've been looking into how to 'fake' cookies with an IInternetProtocol implementation, but have not been able to pass the value to reflect in "document.cookie" to client-side scripting. I guess there's not just one of the BINDSTATUS values you need to report with the data. So I checked what interfaces are requested from my handler. Apparently IE gets a IWinInetHttpInfo, but doesn't call it to get the cookie data. (It also requests these two interfaces, but I have no idea what these are for: {DD1EC3B3-8391-4FDB-A9E6-347C3CAAA7DD} {C7A98E66-1010-492C-A1C8-C809E1F75905} ) Does anybody have any idea how client-side scripting gets it's 'document.cookie' value?
StijnSanders wrote: > I've been looking into how to 'fake' cookies with an IInternetProtocol > implementation, but have not been able to pass the value to reflect in > "document.cookie" to client-side scripting. document.cookie just does InternetGetCookie with the URL of the page. If the page doesn't come from HTTP, I suspect it's not going to work. -- With best wishes, Igor Tandetnik With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC 1925
