I'm calling openssl from Delphi (10.3.1) using the indy libraries. This works perfectly when using a 32 bit application. However when the application is compiled to 64 bits, I get an access violation on this line: rc := EVP_PKEY_set1_RSA(@key, FRSA);
I tried "dropdown", "dropdown-menu" and doesn't work. Do I have to build the Combobox in code with "OnUnknownTag" to make it look good or there is a simpler way?
Hi there. I received a report of someone on the new Galaxy10 cell phone that is getting an error that the IP address is changing and they cannot establish a connection. I had this once with an iPhone too.
My whole application is in SSL and the error message is "The IP you are using is different than the one that initiated the session. Security check failed. Please restart application."
Is there a way to loosen the security of the web application to allow the IP address to dynamically change? I read on-line that the new Galaxy 10 has networking issues so this is probably a flawed product but I wanted to ask the technical question if we can do anything to compensate for this problem.
Embarcadero® Delphi 10 Seattle Version 23.0.20618.2753
Intraweb 15.0.14
TMS pack Pro
FastReport 5
The dll has been running on the serv er since April 20th with a few TMS component issues. Apart from that after there is one issue, there are sites trying to access files which are not where the dll is published resulting in 404 error and one of the dlls, which is an older isapi dll going down, which causes a domino effect.
How can I stop this from happening. I have a robots.text in the same folder as the dll and have User-agent: * Disallow/ inside it.
Thanks
* I tried googling before posting here and came up with nothing.
A bit of background. I have, at a client's site, approx. 6 - 8 Intraweb SA servers running on a virtual Windows 2018 server (using http.sys and running on port 80). I have limited control over what the hosting crowd decide in terms of virus / malware / windows patch update timetables etc. The reason that multiple servers run on one VM is essentially related to costs to the client. Some of the Intraweb servers have 1,000 clients, others have 50! The reason they are SA (instead of a service) is simply to do with ease of monitoring them! Eventually I will develop a "monitoring app" that will tell if a server has stopped etc.
To the issues (and this is more a query if anyone else has struck these):
1) If one of the SA servers is down and a client tries to login they don't get an error. The simply get the login screen for one of the other SAs that is running. Which confuses the client! Is there a way of having a "default" SA server ... like a 404 page!
2) Shutting down one of these SA servers causes Windows Explorer to "lock up"! This is a bit difficult to explain ... but if you close the server and there is then no desktop response. I'm on a remote connection so I know that Windows hasn't locked ... I can still do file transfers etc. If you wait long enough (15 - 30 minutes) Windows does come back (sometimes with the "Explorer has stopped responding message") and you can recover, without a reboot etc. Of course I never have such an issue on my development computer. This may be related to running them as "application" as opposed to services.
Anyway just seeing if anyone else has had such issues.
I recently took over development/maintenance on a project written in Builder C++ 6 and just converted to Indy 10. Some quirky unexpected problems occurred that seem to be related to the error handling. I am pretty much a novice when it comes to Indy so I'm struggling to figure it all out.
Web searches found several comments by RLebeau that said "let the server handle the exceptions". I looked, but never found, for code samples that would clarify what he meant.
In this case TIdTcpServer Execute calls DoPassthruServerExecute, which calls HandleFirstCallerMessage, both of which have try ... catch sections. There is also a TIdTcpClient and a ReceiveThread (TThread, TIdContext which is passed the server context) that has a try .. catch block, and which catches EIdConnClosedGracefully.
I've attached a stripped down code that has all the essential code and error handling. I would greatly appreciate it if someone could take a look at it and let me know if they see any obvious problems or design issues.