Abstract: An editable version of a first web page may be created by first forming a second web page having the first web page as an inline frame. Then an outer frame of the second web page can be created, the outer frame designed to cause a browser rendering the second web page to create objects in the outer frame placed over corresponding objects in the first web page in the inline frame such that user attempts at interaction with the corresponding objects in the first web page are intercepted by the objects in the outer frame.

Abstract: Techniques are disclosed for concurrent preparation of multiple versions of a website. Web page content can be branched in response to a request from a first user to create a working copy of one or more production web pages source documents. Any edits applied to the production version of the documents may be automatically applied to the working copy. Further, the working copy can be edited independently of the production version. The working copy can be promoted to production by replacing the production version with the edited working copy. Any number of separate working copies can be created and edited concurrently with the production version.

Abstract: An HTML document includes a JavaScript element that manages CSRF token use. When the HTML document is rendered, the JavaScript element asynchronously requests a CSRF token from the server. In response, the server generates a JWT using a keyed HMAC algorithm. The resulting JWT, which functions as a CSRF token, is returned to the user where it is stored in a protected variable inside the JavaScript element. The CSRF token is therefore stateless and isn't stored in a server-side repository. When the user later requests access to a server resource, the CSRF token is included in such request. This may be accomplished by adding a hidden input field that includes the CSRF token to the submission that's transmitted to the server. If the server cannot validate the received token using the HMAC key that was originally used to generate the token, the request is considered unauthorized and is not processed.

Abstract: Techniques are disclosed for concurrent preparation of multiple versions of a website. Web page content can be branched in response to a request from a first user to create a working copy of one or more production web pages source documents. Any edits applied to the production version of the documents may be automatically applied to the working copy. Further, the working copy can be edited independently of the production version. The working copy can be promoted to production by replacing the production version with the edited working copy. Any number of separate working copies can be created and edited concurrently with the production version.

Abstract: An HTML document includes a JavaScript element that manages CSRF token use. When the HTML document is rendered, the JavaScript element asynchronously requests a CSRF token from the server. In response, the server generates a JWT using a keyed HMAC algorithm. The resulting JWT, which functions as a CSRF token, is returned to the user where it is stored in a protected variable inside the JavaScript element. The CSRF token is therefore stateless and isn't stored in a server-side repository. When the user later requests access to a server resource, the CSRF token is included in such request. This may be accomplished by adding a hidden input field that includes the CSRF token to the submission that's transmitted to the server. If the server cannot validate the received token using the HMAC key that was originally used to generate the token, the request is considered unauthorized and is not processed.

Abstract: An HTML document includes a JavaScript element that manages CSRF token use. When the HTML document is rendered, the JavaScript element asynchronously requests a CSRF token from the server. In response, the server generates a JWT using a keyed HMAC algorithm. The resulting JWT, which functions as a CSRF token, is returned to the user where it is stored in a protected variable inside the JavaScript element. The CSRF token is therefore stateless and isn't stored in a server-side repository. When the user later requests access to a server resource, the CSRF token is included in such request. This may be accomplished by adding a hidden input field that includes the CSRF token to the submission that's transmitted to the server. If the server cannot validate the received token using the HMAC key that was originally used to generate the token, the request is considered unauthorized and is not processed.

Abstract: Techniques are disclosed for concurrent preparation of multiple versions of a website. Web page content can be branched in response to a request from a first user to create a working copy of one or more production web pages source documents. Any edits applied to the production version of the documents may be automatically applied to the working copy. Further, the working copy can be edited independently of the production version. The working copy can be promoted to production by replacing the production version with the edited working copy. Any number of separate working copies can be created and edited concurrently with the production version.

Abstract: An HTML document includes a JavaScript element that manages CSRF token use. When the HTML document is rendered, the JavaScript element asynchronously requests a CSRF token from the server. In response, the server generates a JWT using a keyed HMAC algorithm. The resulting JWT, which functions as a CSRF token, is returned to the user where it is stored in a protected variable inside the JavaScript element. The CSRF token is therefore stateless and isn't stored in a server-side repository. When the user later requests access to a server resource, the CSRF token is included in such request. This may be accomplished by adding a hidden input field that includes the CSRF token to the submission that's transmitted to the server. If the server cannot validate the received token using the HMAC key that was originally used to generate the token, the request is considered unauthorized and is not processed.

Abstract: Techniques are provided for filtering digital content based on subject matter exclusion tags associated with a target audience. A content author can associate authored content with tag metadata that is representative of the subject matter of the authored content. When searching for content, such as by submitting a query to a search engine, a content consumer can designate exclusion tags corresponding to subject matter that is not of interest. Where one of the content consumer's designated exclusion tags corresponds to the tag metadata designated by a content author for a particular content item, the consumer can be assumed to have no interest in that content item. A content server can prevent such content from being served to the content consumer. This allows the content consumer to more specifically tailor the received content to his/her specific interests, and to specify customizations that exclude unwanted content from content retrieval operations.

Abstract: An editable version of a first web page may be created by first forming a second web page having the first web page as an inline frame. Then an outer frame of the second web page can be created, the outer frame designed to cause a browser rendering the second web page to create objects in the outer frame placed over corresponding objects in the first web page in the inline frame such that user attempts at interaction with the corresponding objects in the first web page are intercepted by the objects in the outer frame.

Abstract: Techniques are disclosed for concurrent preparation of multiple versions of a website. Web page content can be branched in response to a request from a first user to create a working copy of one or more production web pages source documents. Any edits applied to the production version of the documents may be automatically applied to the working copy. Further, the working copy can be edited independently of the production version. The working copy can be promoted to production by replacing the production version with the edited working copy. Any number of separate working copies can be created and edited concurrently with the production version.