Msinet.ocx and provide "client identification" when browsing http / https-VBForums
Results 1 to 8 of 8

Thread: Msinet.ocx and provide "client identification" when browsing http / https

  1. #1

    Thread Starter
    Hyperactive Member
    Join Date
    Jan 2013
    Posts
    455

    Msinet.ocx and provide "client identification" when browsing http / https

    I am puzzled...

    I have and old project, working, which visits websites and parse some important data from it.

    But one of the website passed recently from http to https.

    So ok, I changed the script, adding the "s".

    and setup some code, to change the INET.Protocol to https.

    First run, it does state change 1 2 3 4 9 10, 11.... which is , host resolved, connecting connect, disconnecting disconnected.

    So frustrated, I grab the statechange code, copy past it to a new project.

    Run exactly the same URL, and it WORKED, it grab the website's data correctly.

    hmmmmmmmmm......

    But what, My new development host, is win10, new notebook.

    And the target where the project must work, is win 2003 server, which is from where I read these state change sequence.

    I though, MAYBE my server is getting old and has uncompatible HTTPS sub components from Microsoft?

    I don't know, so asked a customer, hey which server has you, win 2008 server? Can test it for me?

    The customer reply with the same error I have.


    IIRC: MSINET presents itself in the request header like "MSINET 1.0" , or something, so some webservers by security reasons ban that "client name".

    But, if so, why worked in my new clean project?, only because i ran it in win10?



    So, I thinks, is my code or is the webserver?

    I cared about both, the old project and the new project has the same initial propierties of the msinet object. And things like that.

    Is a possibility that the msinet identifies also the projectName when requesting in webserver?



    anyway I find it very ilogical.




    msinet.ocx I am using and distributing is 6 1 98 16.
    Last edited by flyguille; Sep 27th, 2017 at 04:00 PM.

  2. #2

    Thread Starter
    Hyperactive Member
    Join Date
    Jan 2013
    Posts
    455

    Re: Msinet.ocx and provide "client identification" when browsing http / https


  3. #3

    Thread Starter
    Hyperactive Member
    Join Date
    Jan 2013
    Posts
    455

    Re: Msinet.ocx and provide "client identification" when browsing http / https

    I compiled the new fresh project that works for the HTTPS.

    and run alone in win10 , it works.

    and run alone in win7 ultimate , it works.

    and run in the Windows Server 2003 SP2, and It DON'T work!. Same status change sequence as fail.

    my customer, ran it in win7 home, and DON'T work.

    and he also, ran it in win 2008 and DOn'T work.

    What can be wrong?

    The first things I think, is ok, port to 443 instead 80, but those win7, as we implement it, we don't use the firewall service at all, it is disabled.

    include my w2003 is running without the firewall service. And in it, I installed Firefox, and browsed the same URL without any problem.

    Of course, all machines has the msinet.ocx properly registered and it is the same version.
    Last edited by flyguille; Sep 27th, 2017 at 08:47 PM.

  4. #4

    Thread Starter
    Hyperactive Member
    Join Date
    Jan 2013
    Posts
    455

    Re: Msinet.ocx and provide "client identification" when browsing http / https

    I thinks I found it,

    Internet EXPLORER 9.x ,Internet EXPLORER 8.x, 6.x don't work on https with MSINET.

    Internet Explorer 11.x IT WORKS with MSINET.OCX

    in other words it depends on wininet.dll version!
    Last edited by flyguille; Sep 27th, 2017 at 09:41 PM.

  5. #5

    Thread Starter
    Hyperactive Member
    Join Date
    Jan 2013
    Posts
    455

    Re: Msinet.ocx and provide "client identification" when browsing http / https

    Quote Originally Posted by flyguille View Post
    I thinks I found it,

    Internet EXPLORER 9.x ,Internet EXPLORER 8.x, 6.x don't work on https with MSINET.

    Internet Explorer 11.x IT WORKS with MSINET.OCX

    in other words it depends on wininet.dll version!

    It is confirmed:

    MSINET + HTTP works with all IE versiones.

    MSINET + HTTPS works only with IE11 version. (unknow if with IE10, but not with IE9).


    I wonders WHY?

  6. #6
    Addicted Member
    Join Date
    Apr 2017
    Posts
    180

    Re: Msinet.ocx and provide "client identification" when browsing http / https

    Bummer

  7. #7

    Thread Starter
    Hyperactive Member
    Join Date
    Jan 2013
    Posts
    455

    Re: Msinet.ocx and provide "client identification" when browsing http / https

    Well guys, I am forcing to clients to install IE11, but not all can do it, the IE11 installer throws several errors, a complete nightmare, which normally require to WINDOWS UPDATE hours and hours, and then try again to install IE11 if it don't comes within an update.


    Is there a way to do HTTPS without using MSINET?, I mean calling wininet.dll directly. Anyone has a code for that? and that it works with several versions of IE?

  8. #8
    PowerPoster
    Join Date
    Feb 2006
    Posts
    17,493

    Re: Msinet.ocx and provide "client identification" when browsing http / https

    IE11 has updated SLL/TLS support, pretty old news:

    IE11 Automatically Makes Over 40% of the Web More Secure While Making Sure Sites Continue to Work

    Most likely your issue has nothing to do with MSInet or WinInet or even IE, since all of these are related. Instead the server has probably been updated in order to require the newer cipher suites. So installing IE 11 takes care of all of it at once on the client side.

    WinHttp doesn't use any of the Urlmon/WinInet/IE plumbing, so you might try that.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Featured


Click Here to Expand Forum to Full Width

Survey posted by VBForums.