Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method for utilizing aspect oriented programming on a server, the method comprising: subjecting a HTML layout container to aspect oriented programming on a server-side; tagging the HTML layout container with a class name representing a sensitive aspect of the HTML layout container to separate the tagged HTML layout container from non-sensitive HTML layout containers to prevent unauthorized access to sensitive program objects in the tagged HTML layout container from client-side mechanisms, wherein the sensitive aspect comprises at least one of a security, access control and compliance aspect of the HTML layout container and the non-sensitive aspect comprises at least one of a content, presentation or behavior aspect of the HTML layout container; receiving a request from a browser for the HTML layout container; locating the HTML layout container on the server-side; determining at a server framework if a HTML page of the HTML layout container is being served to a browser authorized to access program objects contained in the HTML layout container tagged with the sensitive aspect class name on a client-side; acting on the determination for the HTML page of the HTML layout container; performing JavaScript code that is tagged to be performed by the server-side; and stripping out the JavaScript code that is tagged to only be performed by the server-side from the HTML page of the HTML layout container.
A server-side method employs aspect-oriented programming for securing HTML layout containers. The method involves: applying aspect-oriented programming to an HTML layout container on the server; tagging the container with a class name to distinguish sensitive aspects (security, access control, compliance) from non-sensitive aspects (content, presentation, behavior), preventing unauthorized client-side access to sensitive program objects. When a browser requests the container, the server framework checks if the browser is authorized to access the tagged sensitive objects. Based on authorization, the server acts accordingly. Server-side JavaScript code is executed, and JavaScript code intended solely for server-side execution is removed from the HTML page before delivery to the browser.
2. A system for utilizing aspect oriented programming on a server, the system comprising: a HTML layout container; a network; a browser in communication with the HTML layout container over the network, the browser having means for calling the HTML layout container; a server comprising means for subjecting the HTML layout container to aspect oriented programming, means for tagging the HTML layout container with a class name representing a sensitive aspect of the HTML layout container to separate the tagged HTML layout container from non-sensitive HTML layout containers to prevent unauthorized access to sensitive program objects in the tagged HTML layout container from client-side mechanisms, wherein the sensitive aspect comprises at least one of a security, access control and compliance aspect of the HTML layout container and the non-sensitive aspect comprises at least one of a content, presentation or behavior aspect of the HTML layout container, means for receiving a call from the browser for the HTML layout container, means for locating the HTML layout container on the server, means for determining if a HTML page of the HTML layout container is being served a browser authorized to access program objects contained in the HTML layout container tagged with the sensitive aspect class name on a client-side, means for acting on the determination for the HTML page of the HTML layout container, means for performing JavaScript code that is tagged to be performed by the server-side, and means for stripping out the JavaScript code that is tagged to only be performed by the server-side from the HTML page of the HTML layout container.
A system that secures HTML layout containers via aspect-oriented programming on a server. The system includes: an HTML layout container; a network; a browser for calling the container; and a server. The server applies aspect-oriented programming to the container and tags it with a class name, separating sensitive aspects (security, access control, compliance) from non-sensitive aspects (content, presentation, behavior). This tagging prevents unauthorized client-side access to sensitive program objects. The server receives browser requests for the container, locates it, and determines if the requesting browser is authorized to access sensitive tagged program objects. Based on authorization, the server acts. Server-side JavaScript code is executed, and JavaScript code intended only for server-side execution is removed from the HTML page before sending it to the browser.
3. The method according to claim 1 wherein the performing of the JavaScript code that are tagged to be performed by the server-side is set to runat=“server” or runat=“both”.
In the method of securing HTML layout containers via aspect-oriented programming (as described: applying aspect-oriented programming to an HTML layout container on the server; tagging the container with a class name to distinguish sensitive aspects (security, access control, compliance) from non-sensitive aspects (content, presentation, behavior), preventing unauthorized client-side access to sensitive program objects; receiving a browser request, checking browser authorization, acting based on authorization, executing server-side Javascript and stripping server-only Javascript), the execution of JavaScript code intended for the server-side is specified using the attributes `runat="server"` or `runat="both"`. This determines where the JavaScript code is executed (server only or both client and server).
4. The method according to claim 1 wherein the stripping of the JavaScript code that is tagged to only be performed by the server-side is set to runat=“server.”
In the method of securing HTML layout containers via aspect-oriented programming (as described: applying aspect-oriented programming to an HTML layout container on the server; tagging the container with a class name to distinguish sensitive aspects (security, access control, compliance) from non-sensitive aspects (content, presentation, behavior), preventing unauthorized client-side access to sensitive program objects; receiving a browser request, checking browser authorization, acting based on authorization, executing server-side Javascript and stripping server-only Javascript), the removal of JavaScript code intended only for server-side execution from the HTML page is specified using the attribute `runat="server"`. This ensures that the code is removed before sending the page to the browser.
5. The method according to claim 1 wherein the stripping of the JavaScript code that is tagged to only be performed by the server-side is set to runat=“server-proxy.”
In the method of securing HTML layout containers via aspect-oriented programming (as described: applying aspect-oriented programming to an HTML layout container on the server; tagging the container with a class name to distinguish sensitive aspects (security, access control, compliance) from non-sensitive aspects (content, presentation, behavior), preventing unauthorized client-side access to sensitive program objects; receiving a browser request, checking browser authorization, acting based on authorization, executing server-side Javascript and stripping server-only Javascript), the removal of JavaScript code intended only for server-side execution from the HTML page is specified using the attribute `runat="server-proxy"`. This attribute likely indicates a specific proxy mechanism used for server-side code execution and removal.
6. The method according to claim 1 further comprising: receiving a callback from the authorized browser; and performing callback functions in the callback by the server-side.
In the method of securing HTML layout containers via aspect-oriented programming (as described: applying aspect-oriented programming to an HTML layout container on the server; tagging the container with a class name to distinguish sensitive aspects (security, access control, compliance) from non-sensitive aspects (content, presentation, behavior), preventing unauthorized client-side access to sensitive program objects; receiving a browser request, checking browser authorization, acting based on authorization, executing server-side Javascript and stripping server-only Javascript), the method further includes receiving a callback from an authorized browser and then executing callback functions server-side in response to that callback.
7. The method according to claim 6 further comprising: packaging results of the callback functions by the server-side; and returning the results in a response to the callback by the server-side.
In the method of securing HTML layout containers via aspect-oriented programming with browser callbacks (as described: applying aspect-oriented programming to an HTML layout container on the server; tagging the container; authorizing access; executing server-side Javascript and stripping server-only Javascript; receiving a callback from an authorized browser; and executing callback functions server-side), the server-side then packages the results of executing the callback functions and sends the packaged results back to the browser in response to the callback request.
8. The method according to claim 1 further comprising: receiving a callback from the authorized browser; and performing callback functions in the callback by the server-side.
In the method of securing HTML layout containers via aspect-oriented programming (as described: applying aspect-oriented programming to an HTML layout container on the server; tagging the container with a class name to distinguish sensitive aspects (security, access control, compliance) from non-sensitive aspects (content, presentation, behavior), preventing unauthorized client-side access to sensitive program objects; receiving a browser request, checking browser authorization, acting based on authorization, executing server-side Javascript and stripping server-only Javascript), the method further includes receiving a callback from an authorized browser and then executing callback functions server-side in response to that callback.
9. The method according to claim 8 further comprising: packaging results of the callback functions by the server-side; and returning the results in a response to the callback by the server-side.
In the method of securing HTML layout containers via aspect-oriented programming with browser callbacks (as described: applying aspect-oriented programming to an HTML layout container on the server; tagging the container; authorizing access; executing server-side Javascript and stripping server-only Javascript; receiving a callback from an authorized browser; and executing callback functions server-side), the server-side then packages the results of executing the callback functions and sends the packaged results back to the browser in response to the callback request.
10. A method for utilizing aspect oriented programming on a server, the method comprising: subjecting a HTML layout container to aspect oriented programming on a server-side; tagging the HTML layout container with a class name representing a sensitive aspect of the HTML layout container to separate the tagged HTML layout container from non-sensitive HTML layout containers to prevent unauthorized access to sensitive program objects in the tagged HTML layout container from client-side mechanisms, wherein the sensitive aspect comprises at least one of a security, access control and compliance aspect of the HTML layout container and the non-sensitive aspect comprises at least one of a content, presentation or behavior aspect of the HTML layout container receiving a request from a browser for the HTML layout container; locating the HTML layout container on the server-side; determining at a server framework if a HTML page of the HTML layout container is being served to a browser authorized to access program objects contained in the HTML layout container tagged with the sensitive aspect class name; performing JavaScript code that is tagged to be performed by the server-side; and stripping out the JavaScript code that is tagged to only be performed by the server-side from the HTML page of the HTML layout container; and sending the HTML page of the HTML layout container to the authorized browser.
A server-side method uses aspect-oriented programming to secure HTML layout containers. It involves: applying aspect-oriented programming to an HTML layout container on the server; tagging the container with a class name to distinguish sensitive aspects (security, access control, compliance) from non-sensitive aspects (content, presentation, behavior), preventing unauthorized client-side access to sensitive program objects. When a browser requests the container, the server framework checks if the browser is authorized to access the tagged sensitive objects. Server-side JavaScript code is executed, and JavaScript code intended solely for server-side execution is removed from the HTML page before sending the HTML page to the authorized browser.
11. The method according to claim 10 wherein the performing of the JavaScript code that are tagged to be performed by the server-side is set to runat=“server” or runat=“both”.
In the method of securing HTML layout containers via aspect-oriented programming (as described: applying aspect-oriented programming to an HTML layout container on the server; tagging the container; authorizing access; executing server-side Javascript and stripping server-only Javascript and sending HTML page), the execution of JavaScript code intended for the server-side is specified using the attributes `runat="server"` or `runat="both"`. This determines where the JavaScript code is executed (server only or both client and server).
12. The method according to claim 10 wherein the stripping of the JavaScript code that is tagged to only be performed by the server-side is set to runat=“server.”
In the method of securing HTML layout containers via aspect-oriented programming (as described: applying aspect-oriented programming to an HTML layout container on the server; tagging the container; authorizing access; executing server-side Javascript and stripping server-only Javascript and sending HTML page), the removal of JavaScript code intended only for server-side execution from the HTML page is specified using the attribute `runat="server"`. This ensures that the code is removed before sending the page to the browser.
13. The method according to claim 10 wherein the stripping of the JavaScript code that is tagged to only be performed by the server-side is set to runat=“server-proxy.”
In the method of securing HTML layout containers via aspect-oriented programming (as described: applying aspect-oriented programming to an HTML layout container on the server; tagging the container; authorizing access; executing server-side Javascript and stripping server-only Javascript and sending HTML page), the removal of JavaScript code intended only for server-side execution from the HTML page is specified using the attribute `runat="server-proxy"`. This attribute likely indicates a specific proxy mechanism used for server-side code execution and removal.
14. The method according to claim 10 further comprising: receiving a callback from the authorized browser; and performing callback functions in the callback by the server-side.
In the method of securing HTML layout containers via aspect-oriented programming (as described: applying aspect-oriented programming to an HTML layout container on the server; tagging the container; authorizing access; executing server-side Javascript and stripping server-only Javascript and sending HTML page), the method further includes receiving a callback from an authorized browser and then executing callback functions server-side in response to that callback.
15. The method according to claim 14 further comprising: packaging results of the callback functions by the server-side; and returning the results in a response to the callback by the server-side.
In the method of securing HTML layout containers via aspect-oriented programming with browser callbacks (as described: applying aspect-oriented programming to an HTML layout container on the server; tagging the container; authorizing access; executing server-side Javascript and stripping server-only Javascript and sending HTML page; receiving a callback from an authorized browser; and executing callback functions server-side), the server-side then packages the results of executing the callback functions and sends the packaged results back to the browser in response to the callback request.
16. The method according to claim 10 further comprising: receiving a callback from the authorized browser; and performing callback functions in the callback by the server-side.
In the method of securing HTML layout containers via aspect-oriented programming (as described: applying aspect-oriented programming to an HTML layout container on the server; tagging the container; authorizing access; executing server-side Javascript and stripping server-only Javascript and sending HTML page), the method further includes receiving a callback from an authorized browser and then executing callback functions server-side in response to that callback.
17. The method according to claim 16 further comprising: packaging results of the callback functions by the server-side; and returning the results in a response to the callback by the server-side.
In the method of securing HTML layout containers via aspect-oriented programming with browser callbacks (as described: applying aspect-oriented programming to an HTML layout container on the server; tagging the container; authorizing access; executing server-side Javascript and stripping server-only Javascript and sending HTML page; receiving a callback from an authorized browser; and executing callback functions server-side), the server-side then packages the results of executing the callback functions and sends the packaged results back to the browser in response to the callback request.
Unknown
August 12, 2014
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.