Used the provided login macro partial script when assigning public access to a node. All works well in Visual Studio. When deployed to Azure it goes into an endless redirect loop.
Now I'm guessing this because the provided login macro partial script saves the originally requested URL in session and good old Azure doesn't do sessions.
Can anyone give me a heads up as to how to get around this? Is there some way of doing it that will work in Visual Studio AND Azure?
Do I really need to go to all the trouble and expense of setting up a Redis Cache service on Azure just to hold a returnURL for the odd user that's going to login to a maintenance screen? It seems overkill. Doesn't Umbraco have it's own caching that can be used with Azure?
Public Access Login Script on Azure
V7.3.3 Visual Studio/Azure web site
Used the provided login macro partial script when assigning public access to a node. All works well in Visual Studio. When deployed to Azure it goes into an endless redirect loop.
Now I'm guessing this because the provided login macro partial script saves the originally requested URL in session and good old Azure doesn't do sessions.
Can anyone give me a heads up as to how to get around this? Is there some way of doing it that will work in Visual Studio AND Azure?
Any thoughts appreciated,
Craig
Do I really need to go to all the trouble and expense of setting up a Redis Cache service on Azure just to hold a returnURL for the odd user that's going to login to a maintenance screen? It seems overkill. Doesn't Umbraco have it's own caching that can be used with Azure?
Any advice appreciated.
is working on a reply...