Tickets :: Comment on [#13284] Horde_Secret: Only store key in cookies if cookies are in use

Search Results: 82 of 248 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: __.. ..__..__ .__. (__ \| \|[__][ __[__] .__)\|/\\|\| \|[_./\| \|
Comment	> Side note: Cookies are officially not supported for WebDAV sessions (yunosh) > > See also: > http://comments.gmane.org/gmane.comp.php.sabredav/65 > > "2. Don't use sessions in WebDAV. They are not supported in most > clients, and generally a terrible idea. HTTP is supposed to be > stateless. Only when your client is a browser, a (session-)cookie is > acceptable." > > and > > http://stackoverflow.com/questions/14499686/mac-os-x-does-not-send-cookies-to-webdav-resource > > We probably need to come up with a more clever storage mechanism. > Funny the previous code worked at all for DAV. > > Wild guess: The webdav access generates a new "session id" on every > page access since it does not transport the session id cookie. This > breaks Horde_Secret because it can no longer decrypt the data of the > previous page access. >
Attachment
Watch this ticket