#sessionstorage

Apigee는 구글에 인수된 솔루션으로 API 프록시 개발을 위해 별도의 사이트가 존재한다. https://apigee.google.com 근데 구글은 이렇게 서브 도메인으로 독립되어 있는 솔루션의 UI를 GCP 콘솔로 합치려는 시도를 꾸준히 하고 있다. Apigee도 그렇다. 또 한 편으로 Apigee도 프록시 개발을 위한 화면이 Classic UI와 New UI가 있는데 각각 쓰기 좋은 부분도 있지만 확실한건 New UI가 기본값이다. 그런데 New UI에서 Class UI로 바꾸고 나서 다시 New UI를 클릭하면 GCP 콘솔로 이동해버린다… 이 상황을 해결하려면 브라우저의 LocalStorage에 ENABLE_PROXY_EDITOR_v2_BY_DEFAULT의 값을 true로 바꾸고 다시…

How to Store temporary Form Data in an Angular and SessionStorage ☞ https://morioh.com/p/6c30d73e43c8

http://jsbin.com/qelilih/edit?js,console

sessionStorage.setItem('good', null);

const good = sessionStorage.getItem('good');

console.log(good, typeof good);

/** "null" "string" */

sessionStorage.removeItem('good');

const good2 = sessionStorage.getItem('good');

console.log("-------------------------------------------- //");

console.log(good2, typeof good2, (good2), !good2); // null

The core argument used against Web Storage says because Web Storage doesn't support cookie-specific features like the Secure flag and the HttpOnly flag, it's easier for attackers to steal it. The path attribute is also cited. I'll take a look at each of these features and try to examine the history of why they were implemented, what purpose they serve and whether they really make cookies the best choice for session tokens.

...

The HttpOnly flag is an almost useless XSS mitigation. It was invented back in 2002 to prevent XSS being used to steal session tokens. At the time, stealing cookies may have been the most popular attack vector - it was four years later that CSRF was described as the sleeping giant. Today, I think any competent attacker will exploit XSS using a custom CSRF payload or drop a BeEF hook. Session token stealing attacks introduce a time-delay and environment shift that makes them impractical and error prone in comparison - see Why HttpOnly Won't Protect You for more background on why. This means that if an attacker is proficient, HttpOnly won't even slow them down. It's like a WAF that's so ineffective attackers don't even notice it exists. ...

If you want to save the previous pageName via DTM without a Plugin (getPreviousValue), you can use Session Storage. Two Pageload Rules are needed.

First PLR: - Trigger Rule at “DOM Ready” - Rule Condition: Path “.*” (regex enabled) - Custom Code “None-Sequential Javascript”:

if(typeof(Storage) != "undefined") { if (typeof(s) !== "undefined") { sessionStorage.pagename = s.pageName; } }

Second PLR: - Trigger Rule at “Bottom of Page” - Rule Condition: Path “.*” (regex enabled) - Rule Condition: Custom:

if(typeof(Storage) !== "undefined") { if(typeof(sessionStorage.getItem("pagename")) != "undefined") { var prevPageName = sessionStorage.getItem("pagename"); _satellite.setVar("previousPage",prevPageName); return true; } }

- Adobe Analytics: prop2 set as %previousPage%

ngStorage localStorage and sessionStorage done right for AngularJS

ngStorage localStorage and sessionStorage done right for AngularJS

An AngularJS module that makes Web Storage working in the Angular Way. Contains two services:$localStorage and $sessionStorage.

Differences with Other Implementations

No Getter ‘n’ Setter Bullshit– Right from AngularJS homepage: “Unlike other frameworks, there is no need to […] wrap the model in accessors methods. Just plain old…