Hi demis,
we are building an api with ss. the client are mobile apps and a webbrowser app based on angularjs. we don’t want to use cookies. after reading the documentation https://github.com/ServiceStack/ServiceStack/wiki/Sessions#use-http-headers-to-send-session-cookies I expect to be able to login and then send in the future calls the ss-id in the http-header (X-ss-id). somehow i couldn’t manage to get it work.
i’m not sure if this is a bug or if i misunderstood your documentation.
anyway, i’ve writte a test to simulate what i want to do:
https://github.com/tobiaszuercher/ServiceStack/commit/d3ba20c0e38735cd00a147f2388b99cad8ca8776
I think the expectation i’ve from the documentation can’t work because it will add a TemporarySession if there is no ss-id found in the cookie in https://github.com/ServiceStack/ServiceStack/blob/master/src/ServiceStack/SessionFeature.cs#L35-40.
Thanks for any help in advance!
tobi
Yeah this was an issue that’s been resolved in this commit:
https://github.com/ServiceStack/ServiceStack/commit/8a479eed76ec54effe5c186345465c501a6366e7
It’s resolved in the v4.0.37 pre-release version that’s now on MyGet:
https://github.com/ServiceStack/ServiceStack/wiki/MyGet
Tobias Zürcher:
thank you demis. we are using the preview version now and everything is ok! hope this is pushed to the official nuget repo soon! thx for your fast response, apprechiated!