So either it will be available for use when app will be ready or there will be some kind of fallback for ssl connections. However Chrome team is working on it right now. Now there's no limitations for HTTP request but it is a javascript's implementation for HTTP communication.Ĭurrently (May 12, 2014) Chrome socket API do not support SSL connections. This project's version is based on Chrome's socket's API. can't read some response headers like Cookie (because of security issues).can't set some request headers listed in the spec as available only for browser to set.Previous version was based on XMLHttpRequest with all it's limitations: Most relevant change since last version is HTTP connection engine. Since it is not possible to upgrade legacy apps to new Chrome Apps it will be new application. Source code for previous app can be found at Google Code.Īnd working app can be found in Chrome Web Store However, since Java can't be so flexible to meet app's requirements I decided to rewrite the app. Previous version was done using Google Web Toolkit. This is a next version of the Chrome Legacy App. Refactor these functionalities as configurable "middlewares" so that it becomes more useful for other developers using the tool outside of FlyVictor etc.) (other ideas for this fork, is to handle authentication automatically as well. The secret can be set as an option in the Request page (if it is not set, then no signature is appended). FlyVictor fork adds the ability to append signatures to requests, it calculates the oauth_signature value according to the spec and appends to the request.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |