Time goes on

Nope, I haven't forgot about my favorite application.
I just changing my job right now and I don't have time to code lately... I read your comments on application profile and reported issues on Google Developers. But I need more time to work wit this. So be patient, report new bugs (if any :) and I will take care of it.

Happy RESTing :)

P.S.
If you curious about my new company it's interactive agency Kalicinscy.com :)

Applications server version.

Hi,
Lately I worked about application performance. I did a lot of improvements, but it is not a subject of this post.
I like to announce that server side application is working from now at http://chromerestclient.appspot.com/
After you log in you can view all data that you've sent to server and delete it if you need.
On this site you can remove all your data as well (including connection to your Google account).

If you have any suggestions write email to me or create issue ticket at http://code.google.com/p/chrome-rest-client/issues/list

Cheers!

Permissions chage - conclusion

I've noticed that many of You asked me about new permissions in application.
What can I say more? Permission change was noted in applications description and on this blog post.

Application won't send any of your data to any server and I will not use it for any purpose. You can make sure about this by checking source code (http://code.google.com/p/chrome-rest-client/source/browse/#svn%2Ftrunk%2FRestClientApp) or just opening chrome inspector (ctrl + shift + i) and check is any data are send somewhere.


I don't feel like deserve for lower rating just because You can't read :)

Cheers!

Export data from application

It is big problem to export saved request to a file within an chrome application. HTML5 (either javascript) don't have any API to save any data in file (outside applications sandbox).
Normally with application backed it would generate this file on server side and pass it to browser as a file.
In Chrome environment  it is not possible. There is no backed and can't force browser to generate file.

Anyway, lately I've started writing application backend on Google App Engine. It will have ability to save form data and restore it on demand. It also will have ability to share this data.

It will be available in future release.

New permissions - re-enable your application

As you may noticed lately an application has been disabled by Chrome browser. I'ts because I've changed permissions for application. I've added "history" permission to application to make typing URL easier.

Prior current version you had to type all URL manually. Now using history API application can recognize URL you want to type and suggest it (if you had visited this URL earlier).

I hope you appreciate new change.

As always you can check source code to make sure you history is not misused:
revision change: http://code.google.com/p/chrome-rest-client/source/detail?r=109
history usage: http://code.google.com/p/chrome-rest-client/source/browse/trunk/RestClientApp/src/com/restclient/client/storage/UrlsSuggestOracle.java
API access:

• http://code.google.com/p/chrome-rest-client/source/browse/trunk/RestClientApp/src/com/restclient/client/chrome/History.java
• http://code.google.com/p/chrome-rest-client/source/browse/trunk/RestClientApp/src/com/restclient/client/chrome/HistoryItem.java
• http://code.google.com/p/chrome-rest-client/source/browse/trunk/RestClientApp/src/com/restclient/client/chrome/HistorySearchCallback.java

Cookies capture - experimental feature. Give feedback!

Lately, I worked about cookie capture during request. It is not so simple as You can imagine.
Application use XMLHttpRequest class in javascript to handle requests. According to w3c spec it can't read some headers. One of it is "Set-Cookie" witch is responsible to set cookie on client. That's why I do not show cookies bar as an response to HTTP request.
Fortunately it is still chrome application and applications/extensions can read cookies. But, I can't read cookies from particular server response. I can handle all cookies change in all tabs, in all windows. It's kinda tricky because you don't know witch request actually creates the cookie.
So. When You start request application record all cookies that has been changed during this request. When response is loaded application stops recording cookies change and display results (if any recorded).

But I noticed that not always cookies are recorded during request. Sometimes they are set just after response is loaded and application already retrieved cookies list. This cookies will not be displayed. So when application creating response view it call delayed function (about 200ms) to get cookies after some time (when browser probably set does cookies).

I hope this will be good enough to make application more helpful.
If You have suggestions or have issue with cookies give feedback (google code issue tracker or in comments :)

Oh. Cookies capture in application is experimental feature and is disabled by default. To enable it go to "options" and check checkbox under "cookie capture".

Application has back to Web Store

Google Chrome Web Store abuse team checked my application and they determined that Chrome Rest Client has passed  the security compliance investigation.

The application is available at Chrome Webstore again.