Source: {"pile_set_name": "USPTO Backgrounds"}

In some environments, a request for a network resource must be accompanied by state information indicating the requester has access to the resource. For example, a server may require an authorization cookie to be present in a request for a given document. This state information is typically managed by a web browser.
However, there may be many cases where a user is navigating resources using a web page, and then selects a resource which requires an application other than the web browser to be viewed. In some cases, the web browser and the other application may be part of a virtualized computing environment. For example, a user may be navigating a web site and click on a link to a spreadsheet, causing the browser to launch a remotely hosted spreadsheet application for viewing the viewing. When the application hosted by a server is invoked for the purposes of loading the external HTTP-based resource, the application may be required to include state information for the request to be allowed. Some systems may lack a mechanism for injecting the necessary session state data into an upstream request. For example, in some systems, the link between the application and the external HTTP-based resource is provided directly by a file including connection information but lacking necessary session state data.
One result of lacking the necessary session state data may be presentation of a session failure message or error dialog box to a user of the system. Another result in cases where the application hosted on the application server supports rending of HTML (applications such as WORD, EXCEL, or POWERPOINT), may be the rendering of an error page within the application, such that the error page is presented as if it were the requested resource. This may cause confusion to the user.
Thus there exists a need for systems and methods which allow access of remote resources in launched applications while preserving state information necessary for the request.