Abstract: Representational state transfer (REST) based geo-aware content transfer includes a REST server configured for receiving an application programming interface (API) request from a client device. The REST server obtains a upload universal resource locator (URL) targeting a caching server that is geographically closest to the client device, constructs an upload link containing the upload URL and a completion callback, and sends the upload link to the client device. The client device uses the upload URL to upload content to the caching server. The caching server interprets the completion callback to obtain a completion URL and, upon completion of content uploading, makes a REST API call using the completion URL. Responsive to the REST API call, the REST server executes an inbound operation to complete the uploading to a content management system and returns the content URL to the caching server which sends the content URL to the client device.

Abstract: Representational state transfer (REST) based geo-aware content transfer includes a REST server configured for receiving an application programming interface (API) request from a client device. The REST server obtains a upload universal resource locator (URL) targeting a caching server that is geographically closest to the client device, constructs an upload link containing the upload URL and a completion callback, and sends the upload link to the client device. The client device uses the upload URL to upload content to the caching server. The caching server interprets the completion callback to obtain a completion URL and, upon completion of content uploading, makes a REST API call using the completion URL. Responsive to the REST API call, the REST server executes an inbound operation to complete the uploading to a content management system and returns the content URL to the caching server which sends the content URL to the client device.

Abstract: Representational state transfer (REST) based geo-aware content transfer includes a REST server configured for receiving an application programming interface (API) request from a client device. The REST server obtains a upload universal resource locator (URL) targeting a caching server that is geographically closest to the client device, constructs an upload link containing the upload URL and a completion callback, and sends the upload link to the client device. The client device uses the upload URL to upload content to the caching server. The caching server interprets the completion callback to obtain a completion URL and, upon completion of content uploading, makes a REST API call using the completion URL. Responsive to the REST API call, the REST server executes an inbound operation to complete the uploading to a content management system and returns the content URL to the caching server which sends the content URL to the client device.

Abstract: A system comprising a processor and a computer readable memory coupled to the processor, the computer-readable memory comprising computer program code executable by the processor to generate create a self-signed certificate, create a second certificate using the set of certificate generation parameters, the second certificate linked to the self-signed certificate, store the self-signed certificate in a certificate store of a first web browser; and store the second certificate in a local server certificate store to allow a local service to use the second certificate in a handshake to establish a secure socket connection with the first web browser in compliance with a mixed content security policy of the first web browser.

Abstract: A system comprising a processor and a computer readable memory coupled to the processor, the computer-readable memory comprising computer program code executable by the processor to generate create a self-signed certificate, create a second certificate using the set of certificate generation parameters, the second certificate linked to the self-signed certificate, store the self-signed certificate in a certificate store of a first web browser; and store the second certificate in a local server certificate store to allow a local service to use the second certificate in a handshake to establish a secure socket connection with the first web browser in compliance with a mixed content security policy of the first web browser.

Abstract: A system comprising a processor and a computer readable memory coupled to the processor, the computer readable memory configured with a page processable by page processing code. The page can be configured to generate a set of random connection data usable by a local server program instance to verify that a connection request is from the page, launch the local server program instance, provide the set of random connection data to the local server program instance, create a client socket instance, send a connection request to the local server program instance to establish a connection between the client socket instance and a server socket instance of the server program instance and based on an acceptance of the connection request by the server program instance, complete the connection. The connection may be usable for bi-directional communication between the page and local server program instance.

Abstract: A system comprising a processor and a computer readable memory coupled to the processor, the computer readable memory configured with a page processable by page processing code. The page can be configured to generate a set of random connection data usable by a local server program instance to verify that a connection request is from the page, launch the local server program instance, provide the set of random connection data to the local server program instance, create a client socket instance, send a connection request to the local server program instance to establish a connection between the client socket instance and a server socket instance of the server program instance and based on an acceptance of the connection request by the server program instance, complete the connection. The connection may be usable for bi-directional communication between the page and local server program instance.

Abstract: Representational state transfer (REST) based geo-aware content transfer includes a REST server configured for receiving an application programming interface (API) request from a client device. The REST server obtains a upload universal resource locator (URL) targeting a caching server that is geographically closest to the client device, constructs an upload link containing the upload URL and a completion callback, and sends the upload link to the client device. The client device uses the upload URL to upload content to the caching server. The caching server interprets the completion callback to obtain a completion URL and, upon completion of content uploading, makes a REST API call using the completion URL. Responsive to the REST API call, the REST server executes an inbound operation to complete the uploading to a content management system and returns the content URL to the caching server which sends the content URL to the client device.

Abstract: Representational state transfer (REST) based geo-aware content transfer includes a REST server configured for receiving an application programming interface (API) request from a client device. The REST server obtains a upload universal resource locator (URL) targeting a caching server that is geographically closest to the client device, constructs an upload link containing the upload URL and a completion callback, and sends the upload link to the client device. The client device uses the upload URL to upload content to the caching server. The caching server interprets the completion callback to obtain a completion URL and, upon completion of content uploading, makes a REST API call using the completion URL. Responsive to the REST API call, the REST server executes an inbound operation to complete the uploading to a content management system and returns the content URL to the caching server which sends the content URL to the client device.

Abstract: A system comprising a processor and a computer readable memory coupled to the processor, the computer-readable memory comprising computer program code executable by the processor to generate create a self-signed certificate, create a second certificate using the set of certificate generation parameters, the second certificate linked to the self-signed certificate, store the self-signed certificate in a certificate store of a first web browser; and store the second certificate in a local server certificate store to allow a local service to use the second certificate in a handshake to establish a secure socket connection with the first web browser in compliance with a mixed content security policy of the first web browser.

Abstract: A system comprising a processor and a computer readable memory coupled to the processor, the computer readable memory configured with a page processable by page processing code. The page can be configured to generate a set of random connection data usable by a local server program instance to verify that a connection request is from the page, launch the local server program instance, provide the set of random connection data to the local server program instance, create a client socket instance, send a connection request to the local server program instance to establish a connection between the client socket instance and a server socket instance of the server program instance and based on an acceptance of the connection request by the server program instance, complete the connection. The connection may be usable for bi-directional communication between the page and local server program instance.

Abstract: Representational state transfer (REST) based geo-aware content transfer includes a REST server configured for receiving an application programming interface (API) request from a client device. The REST server obtains a upload universal resource locator (URL) targeting a caching server that is geographically closest to the client device, constructs an upload link containing the upload URL and a completion callback, and sends the upload link to the client device. The client device uses the upload URL to upload content to the caching server. The caching server interprets the completion callback to obtain a completion URL and, upon completion of content uploading, makes a REST API call using the completion URL. Responsive to the REST API call, the REST server executes an inbound operation to complete the uploading to a content management system and returns the content URL to the caching server which sends the content URL to the client device.