Closed Aexyn closed 8 years ago
HTTP 1.x is a request/response protocol that involves the client initiating a connection to a server and making a request, then expecting a reply. There is no concept in this system of the server then issueing a request to the client, or a server "connecting back" to the client. You would have to be hosting a web server in your application for this to occur.
That said, if you are using HTTP 2 features, you can indeed have server push messages that don't work in the normal HTTP sense though I strongly doubt that okhttp's network interceptor properly supports this concept based on its API.
Can you please be more (much more) specific about how your protocol actually works so we can try to figure out what Stetho can do to help?
Closing due to inactivity. Still require an answer to my questions to resolve...
I am trying to integrate
Okhttp3
in my chat app withnew StethoInterceptor
. When I send some message through App, That message is visible inHeader Tab
of the request inNetwork window
ofChrome DevTool
. But When I receive some message, It is not visible.However when I do the same with this class:
It Works for both incoming and outgoing calls.
It might be possible that there is a switch to activate logging incoming connections that I might not know. Please Help