I can find WL.Client.connect to connect a client - so far so good. How can I do the opposite however? (I have good reason to do this, rest assured.)
I think that for this purpose, what you'd actually need to do is to "restart the session" with the server. Try using WL.Client.ReloadApp.
What do you mean by disconnect? WL app does not maintain an open connection. HTTP connection is closed each time response is returned from a server. Do you mean WL.Client.logout() ?
Related
I am trying to scrape the new.google.com and get some information, I have no issue locally but when I deploy to our Datacenter it fails with "connection refused" that means it is blocked.
Get https://news.google.com?ceid=en%3Agb&gl=en-gb&hl=en-gb&hs=en-gb&pz=1: dial tcp 172.217.5.206:443: connect: connection refused
Do we have any alternative of passing header and by-pass to get unblocked? or is using paid API is the only option if I have to use google for some of my testing?
Did anyone encounter and resolved it?
This is pretty common. Somebody else used the same IP address for scraping or even something worse :) so it's blocked.
You can use some proxy services. There are some with free tier so it will do the job for testing.
And before you ask... free proxy services are super slow and probably already blocked :)
I would like to ask for help.
I am using the mss-4.0.21-wildfly-8.2.1.Final server and the SIP servlet B2B WebSocket sample with some small changes in order to use the Doubango sipML5 client for registering and making call.
When I use the ws protocol, my servlet works fine, I can register and make call with Doubango sipML5 client.
When I use the wss protocol, the register function works fine, but I get the error "Connection Refused" while trying to make call. I checked my servlet code and found that the "Connection Refused" error is at this line outRequest.send();. I think the problem is that my servlet cannot send the INVITE request to callee over wss because it is refused. Now I have no idea about how to solve this problem.
Thus, I would like to ask for any idea about this problem. Thank you very much!
Instead of using the Doubango sipML5, I use the Olympus which is the RestComm WebRTC Application, and everything works fine now.
I need answer to one very basic question.
Is it necessary to have telnet access to hit an API while systems are connected over VPN? For example, if my system exposed an API for other systems to hit and they are connected in VPN using IPsec, does a third party system needs telnet access to my server for using that API? The API uses soap protocol for receiving request and sending response.
(I did not find out the solution using google. The question is so naive that I had to assume everyone must already know the answer and does not bother to discuss it in web. Sorry for bothering with this simple question)
This is very strange. Accessing an http endpoint for anything else than dev using telnet doesn't really make much sense to me. If someone is using telnet to fetch informations from a server in an application. Something is already really wrong. If telnet is timing out while doing http requests. It's not really your fault and you shouldn't have to worry about edge cases like this.
If the dev is using telnet to discover security issues. This is a different issue and you could probably log anything that come from this particular client. If you gave hime some credentials, it should be easy to find who is doing which request. (I believe you might be already doing this).
You should probably ask the dev "why are you using telnet?". If for whatever reason the dev though he could send a plain SOAP request to your server using telnet without sending HTTP headers and so on.... then yes the connection is likely to timeout because the server isn't going to handle the request.
In my twisted mind, I can imagine some kind of legacy application calling scripts that open telnet sessions to parse some data and return the "parsed" data to the patched legacy project that doesn't handle http/tcp. I'd have in mind some sort of old Cobol application. Much more easier to do system call than to rewrite the whole thing to support APIs.
If for whatever reason, the client claims that telnet is needed for whatever reason. You can tell him back that telnet shouldn't be considered secure. Your api can be accessed using https. As far as I remember telnet doesn't encrypt anything unless you send encrypted data. If your client was able to hack a solution using telnet, I'm pretty sure they can hack a different solution wich use an actual http client.
how can I check that server supports keep-alive ?
I want to check this by analyzing http response.
I am using mongoose c++ server. and I am setting header keep-alive.
But I doubt it is closing the connection. As it is always taking time required to connect to host from client. I doubt connection is getting close.
How I can check that connection is getting closed or not ?
The "close" takes place on the TCP level - so IMHO the most relaibale place to check for it is the network level - you can check that by using Fiddler or Wireshark...
I recently got into this article. It makes a chat server and people can connect to it like an AIM. The problem how would I disconnect from the server from the client. Because if I close the client application when its connected to the server it will crash the server as well. Please let me know if anyone has any solutions...
Thanks
Wherever in your code the crash is occurring, you need to set a try/catch block to catch a Connection Closed exception.