For ASP.NET Core 2.1 and 2.2 In the ConfigureServices method of the Startup class, Set options.CheckConsentNeeded = context => false; as follows: services.Configure<CookiePolicyOptions>(options => { // This lambda determines whether user consent for non-essential cookies is needed for a given request. options.CheckConsentNeeded = context => false; options.MinimumSameSitePolicy = SameSiteMode.None; }); Problem solved!
The solution you propose seems like it would work, as long as you don’t mind non-authorized people being able to view the non-secure (http) part of the site ‘as if they are logged in’ – ie as long as the http part of the site does not contain any sensitive information, and the only difference … Read more
The “Filter As Resource” is a perfect tact for this. You can PUT the filter definition to the filter resource, and it can return the filter ID. PUT is idempotent, so even if the filter is already there, you just need to detect that you’ve seen the filter before, so you can return the proper … Read more
You can just do . $profile to source the profile again.
You can get a request parameter id using the expression: <h:outputText value=”#{param[‘id’]}” /> param—An immutable Map of the request parameters for this request, keyed by parameter name. Only the first value for each parameter name is included. sessionScope—A Map of the session attributes for this request, keyed by attribute name. Section 5.3.1.2 of the JSF … Read more
Pros: It’s easy– no app changes required. Better utilizes local RAM caches (e.g. look up user profile once, cache it, and can re-use it on subsequent visits from same user) Cons: If the server goes down, session is lost. (Note that this is a con of storing session info locally on the web server, not … Read more
Here is a kind of snippet for you: app.factory(‘Session’, function($http) { var Session = { data: {}, saveSession: function() { /* save session data to db */ }, updateSession: function() { /* load data from db */ $http.get(‘session.json’).then(function(r) { return Session.data = r.data;}); } }; Session.updateSession(); return Session; }); Here is Plunker example how you … Read more
Firstly, is this method correct? Is there a way without touching the ServletAPI? You can use ExternalContext#invalidateSession() to invalidate the session without the need to grab the Servlet API. @ManagedBean @SessionScoped public class UserManager { private User current; public String logout() { FacesContext.getCurrentInstance().getExternalContext().invalidateSession(); return “/home.xhtml?faces-redirect=true”; } // … } what will happen to my current … Read more
Another option would be modifying web.xml. Prior you must call grails install-templates Then edit src/templates/war/web.xml and add/modify after servlet-mapping: <session-config> <session-timeout>60</session-timeout> </session-config> The value of session-timeout uses minutes as unit.