Hi developers,
For some time now I am working on completely new version of the ARC. Don't worry, it will be the same good and simple tool for testing API calls. However a lot will change in the background. It will allow me to move the app to new platforms other than Chrome ecosystem.
According to app's roadmap ARC will be re-modulated and each part of the app (as a web component) publicly available on GitHub. It helps both the app to transform into new set of tools available everywhere and openness so everyone can use this web components in their projects. This is my contribution to the development of the open web and I deeply believe that this will help in overall web development.
Showing posts with label Chrome app. Show all posts
Showing posts with label Chrome app. Show all posts
Monday, 26 September 2016
Friday, 13 May 2016
ARC cookie exchange extension
Missing cookies?
Advanced REST Client is not able to read cookies set in Chrome browser. If you authenticated yourself in a Chrome tab cookies are not transferred automatically.
But not anymore!
Advanced REST Client is not able to read cookies set in Chrome browser. If you authenticated yourself in a Chrome tab cookies are not transferred automatically.
But not anymore!
Tuesday, 26 April 2016
Session management aka cookies in Advanced REST Client
In recent update there is a new session management mechanism. After last big update some of you complained about lack of cookies support. The networking in Chrome apps is separated from Chrome. Therefore it wasn't possible (and still isn't) to use cookies set in Chrome tab.
Monday, 22 February 2016
HTTP client on chrome.socket.tcp
Hi developers,
Many of you asked me about the possibility to setting in a request a HTTP headers that are prohibited in XHR. The spec for this object prevents setting headers like User-Agent, Proxy-*, Accept-Encoding etc. I couldn't do much about it, until now.
I'd like to introduce the socket-fetch library that I've made for Advanced Rest Client. It is an implementation of a HTTP client that is using chrome.sockets.tcp API and create connection directly on socket. This means that the app will no longer have any limitations from transport specification (either Fetch or XHR API). It gives you more control over what you are sending to the server and makes the app even more powerful tool for API testing.
Many of you asked me about the possibility to setting in a request a HTTP headers that are prohibited in XHR. The spec for this object prevents setting headers like User-Agent, Proxy-*, Accept-Encoding etc. I couldn't do much about it, until now.
I'd like to introduce the socket-fetch library that I've made for Advanced Rest Client. It is an implementation of a HTTP client that is using chrome.sockets.tcp API and create connection directly on socket. This means that the app will no longer have any limitations from transport specification (either Fetch or XHR API). It gives you more control over what you are sending to the server and makes the app even more powerful tool for API testing.
Subscribe to:
Posts (Atom)
