Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2019-02

using TFPHTTPClient

9 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

AFOR

Hi Folks.

Since last week, I experience some trouble using TFPHTTPClient component on Windows 10. Until last Tuesday, an application built with Lazarus 1.8.4 was running perfectly well. Since then access  to any URL is denied. I have upgraded Lazarus to 2.0 but this changes nothing. The main task of the program is to access URL's using GET procedure and store results into a Firebird database for future use. When I post the request directly onto the internet navigator, I get get the answers correctly. I wonder what suddenly happened ? Trouble with SSL (requests are https requests) ? I can't trace the operations with Lazarus debugger as some where another thread is probably launched and sockets play in the middle.

Do you have any ideas on which direction to go ?
Many thanks,

Antonio

AFOR Software Engineering A. Fortuny Gérant

Reply by email

Michael Van Canneyt
to AFOR
AFOR wrote 15 lines
Hi Folks. Since last week, I experience some trouble using TFPHTTPClient component on Windows 10. Until last Tuesday, an application built with Lazarus 1.8.4 was running perfectly well. Since then access  to any URL is denied. I have upgraded Lazarus to 2.0 but this changes nothing. The main task of the program is to access URL's using GET procedure and store results into a Firebird database for future use. When I post the request directly onto the internet navigator, I get get the answers correctly. I wonder what suddenly happened ? Trouble with SSL (requests are https requests) ? I can't trace the operations with Lazarus debugger as some where another thread is probably launched and sockets play in the middle. Do you have any ideas on which direction to go ?

Clearly something changed last tuesday.
Did you change anything on your windows machine ?
Did you change your FPC installation ?
Could it be that the SSL libs were changed/upgraded ?

Michael.

Reply by email

AFOR

Hi Michael.

Sorry using this method, answering via the group doesn't work actually. Definitely yes. The same application ran without problems on my laptop, where now the applications fails. The only change done on both machines is a Windows update. Neither SSL nor other components did change. More curious, in my development machine (VM using VirtualBox in a Linux box using Windows 10 as well and up to date) continues to run (and compile) the application without problems. I'm looking on what possible difference exists between my development machine and the two others. One difference though: in my development machine, OpenSSl (light version 1.02e x86) has been installed, no SSL libs in the two others.

Antonio

AFOR Software Engineering A. Fortuny Gérant

Reply by email

Michael Van Canneyt
to AFOR
AFOR wrote 12 lines
Hi Michael. Sorry using this method, answering via the group doesn't work actually. Definitely yes. The same application ran without problems on my laptop, where now the applications fails. The only change done on both machines is a Windows update. Neither SSL nor other components did change. More curious, in my development machine (VM using VirtualBox in a Linux box using Windows 10 as well and up to date) continues to run (and compile) the application without problems. I'm looking on what possible difference exists between my development machine and the two others. One difference though: in my development machine, OpenSSl (light version 1.02e x86) has been installed, no SSL libs in the two others.

The application cannot run without SSL libs if you use https, so there must be openssl libraries somewhere on the production machines ?

If the update installed openssl 1.1 libraries, that could be the cause.

Michael.

Reply by email

AFOR
to Michael Van Canneyt

Le 18/02/2019 à 14:43, Michael Van Canneyt via lazarus a écrit :

Show quoted text 25 lines
On Mon, 18 Feb 2019, AFOR via lazarus wrote: > Hi Michael. > > Sorry using this method, answering via the group doesn't work actually. > Definitely yes. The same application ran without problems on my > laptop, where now the applications fails. The only change done on both > machines is a Windows update. Neither SSL nor other components did > change. More curious, in my development machine (VM using VirtualBox > in a Linux box using Windows 10 as well and up to date) continues to > run (and compile) the application without problems. I'm looking on > what possible difference exists between my development machine and the > two others. > One difference though: in my development machine, OpenSSl (light > version 1.02e x86) has been installed, no SSL libs in the two others. The application cannot run without SSL libs if you use https, so there must be openssl libraries somewhere on the production machines ? If the update installed openssl 1.1 libraries, that could be the cause. Michael.

So you mean that installing OpenSSL 1.1 could help ?

AFOR Software Engineering A. Fortuny Gérant

Reply by email

Michael Van Canneyt
to AFOR
AFOR wrote 28 lines
Le 18/02/2019 à 14:43, Michael Van Canneyt via lazarus a écrit : > > > On Mon, 18 Feb 2019, AFOR via lazarus wrote: > >> Hi Michael. >> >> Sorry using this method, answering via the group doesn't work actually. >> Definitely yes. The same application ran without problems on my >> laptop, where now the applications fails. The only change done on both >> machines is a Windows update. Neither SSL nor other components did >> change. More curious, in my development machine (VM using VirtualBox >> in a Linux box using Windows 10 as well and up to date) continues to >> run (and compile) the application without problems. I'm looking on >> what possible difference exists between my development machine and the >> two others. >> One difference though: in my development machine, OpenSSl (light >> version 1.02e x86) has been installed, no SSL libs in the two others. > > The application cannot run without SSL libs if you use https, so there > must be openssl libraries somewhere on the production machines ? > > If the update installed openssl 1.1 libraries, that could be the cause. > > Michael. > So you mean that installing OpenSSL 1.1 could help ?

No, the opposite: it will destroy the setup. The openssl unit does not yet support openssl 1.1.

Michael.

Reply by email

AFOR
to Michael Van Canneyt

Le 18/02/2019 à 15:05, Michael Van Canneyt via lazarus a écrit :

Show quoted text 38 lines
On Mon, 18 Feb 2019, AFOR via lazarus wrote: > Le 18/02/2019 à 14:43, Michael Van Canneyt via lazarus a écrit : >> >> >> On Mon, 18 Feb 2019, AFOR via lazarus wrote: >> >>> Hi Michael. >>> >>> Sorry using this method, answering via the group doesn't work actually. >>> Definitely yes. The same application ran without problems on my >>> laptop, where now the applications fails. The only change done on >>> both machines is a Windows update. Neither SSL nor other components >>> did change. More curious, in my development machine (VM using >>> VirtualBox in a Linux box using Windows 10 as well and up to date) >>> continues to run (and compile) the application without problems. I'm >>> looking on what possible difference exists between my development >>> machine and the two others. >>> One difference though: in my development machine, OpenSSl (light >>> version 1.02e x86) has been installed, no SSL libs in the two others. >> >> The application cannot run without SSL libs if you use https, so >> there must be openssl libraries somewhere on the production machines ? >> >> If the update installed openssl 1.1 libraries, that could be the cause. >> >> Michael. >> > So you mean that installing OpenSSL 1.1 could help ? > No, the opposite: it will destroy the setup. The openssl unit does not yet support openssl 1.1. Michael.

Installing OpenSSL 1.1.0e (Win32OpenSSL_light-1_1_0e.exe) in the laptop changes nothing.
Any other hope ?

AFOR Software Engineering A. Fortuny Gérant

Reply by email

Dennis
to AFOR

Maybe first of all, you use the dll "dependancy walker" find out which ssl dll your exe is using and then right click at the dll file to find out the version number of that dll.

Dennis

Reply by email

AFOR
to Dennis

Le 18/02/2019 à 16:35, Dennis via lazarus a écrit :

Show quoted text 5 lines
Maybe first of all, you use the dll "dependancy walker" find out which ssl dll your exe is using and then right click at the dll file to find out the version number of that dll. Dennis

Hi Dennis.

It works. Within the program the unis OpenSSLis used. In the code, names "ssleay32.dll", "libssl32.dll" and "libeay32.dll" are used. This means that version 1.1 cannot be used. After reinstalling version 1.0.2q and copying all three DLLs in the program's folder, everything returns to work. Well done.
Have a lot of thanks.
This means also that Michael was on the good track too. Windows has probably changed to SSl 1.1 .

AFOR Software Engineering A. Fortuny Gérant

Reply by email