Want to monitor Https traffic from google chrome - google-chrome

I want to monitor Https traffic going out from google chrome.
Is there any possibility to write something in C++ for similar purpose, like some hook.
When I tried to hook in ws2_32::WSASend API and load my dll in chrome, it is causing crash. It look like chrome protects hooking of Windows API. I am more interested in APIs not applications like fiddler which can show Https traffic.
I have also seen google's native-client option but does not think it is useful because any extension need to deploy using google web store which is not a possibility in my case.

Related

Is Postman Chrome Extension marked for deprecation? (Seeking company rep answer)

I've seen conflicting and stale information regarding whether Postman Chrome Extension is marked for deprecation or not. Could someone with direct knowledge address this question?
I need to know if I need to request that my work replace the extension with the native Windows app or not. Does the company intend to keep feature parity?
What's the difference between the Postman plugin and the extension? (since they are different)
The Chrome version of Postman is not using the same runtime for execution of requests & test scripts. It is recommended to transit to the native client. Especially when you plan to use Postman collections with the CLI client Newman.
You can read a blog post of the company on this topic here: Blog post on Chrome Extension vs. native app
We're encouraging Postman Chrome users to transition to the the Mac or Windows app when convenient, and to the Linux app when available, by heading to https://www.getpostman.com/apps and downloading the correct app. Going forward, we will be watching to see how Chrome OS app development proceeds, to make sure we provide the right tools for our community.

Google Drive API / Realtime API on Chrome OS - offline?

Chromebooks etc have offline versions of users' Drive files, so is there a way to use the Realtime API, which though apparently inaccessible offline, does work just fine offline? (my app starts in an 'inMemoryModel' mode).
Problems include that Google disallows cacheing of their API's, and that when a manifest-enhanced single-page web-app is run on a disconnected Chromebook, the user is shown a "This application cannot run offline" screen, or similar.
What if anything, is Google's plan for this, and other similar Drive API situations?

How do I make notications appear on Chrome and Chrome OS, like Pushbullet and Google Now?

Pushbullet and Google Now have notifications, which can pop up depending on time or place or any other trigger. If I have to add this feature to my app, how can I do it?
You have two options:
https://developer.chrome.com/extensions/notifications as pointed out by #Moin in the comments. This will only work for people that decide to install your chrome app on desktop (no support for chrome in Android)
Using the new push notifications APIs as described in
https://developers.google.com/web/fundamentals/getting-started/push-notifications/
The latter is probably recommended if you can live with the following caveats:
It's a bit more basic API
Users needs to opt in via a prompt
The site needs to be https

Chrome extension or chrome app?

I would like to create an extension or app for the Chrome browser which would require access to a user's Google Calender (for creating new appointments).
I am unsure of which technology to better research and use, Chrome extensions or apps. My "app" wouldn't need much of a GUI, so I'm leaning towards extension — but I don't know if this would pose any difficulties for accessing a user's Google Calender to add an event.
Anyone one have any idea which technology is best for this situation, and why? Thanks!
Either, or... Go with an extension if you'd like.
I assume you've looked at the API reference?
https://developers.google.com/google-apps/calendar/
From there, I'd imagine you'd just need OAuth to authenticate the user. Here's the JS library:
https://code.google.com/p/google-api-javascript-client/
There are pros/cons of each types, apps or extensions.
Apps
If you would like to create a client application of Google Calendar which has many rich GUI components, this type will become a better solution.
In addition, Chrome apps can communicate with many hardware devices and other servers. Of course, your Chrome app can become as a server (that is, your app can open a server socket and accept a request from other client apps).
Chrome apps can be executed not depending on your Chrome Web browser. That is, Chrome apps cannot access to a context of your Chrome Web browser.
Probably, you don't want to get the pros above, I guess...
Extensions
If you would like to create a small UI for posting your schedule to Google Calendar, this type will become a better solution.
In addition, Chrome extensions can access to a context of your Chrome Web browser. That is, your extension can get page contents of each tab and inject your CSS and/or JS code. For example, your extension will get a URL of some opened tab and include it in a body of the posted schedule.
Chrome extensions completely depend on your Chrome Web browser. That is, your extension cannot execute independently.
Also, generally, high cost will be needed to develop Chrome apps than Chrome extensions. As the result, you should choose Chrome extensions, I believe.

Is it possible to interact with a local application in a Google Chrome extension?

I have begun using Google Chrome as a primary browser, but I miss my Evernote extension, which can clip a web page directly to the local Evernote application. Is it possible for me to write an extension in Chrome that can do this?
Yes it is possible, through NPAPI, but your local application should be prepared for external communication. Code running in an NPAPI plugin has the full permissions of the current user and is not sandboxed or shielded from malicious input by Google Chrome in any way.
All this is described here:
http://code.google.com/chrome/extensions/npapi.html
To avoid the NPAPI way, another idea would be to communicate with a custom local http server binded to localhost and send requests to it.
Disclaimer: Never tried it but theoretically it should work.
I don't think chrome allows this, simply because it would be dangerous to let plugins have extended priviledges, they even run in an extra, low-rights thread and only communicate with chrome itself through pipes.