HTTPS on wodhttpdlx (General questions)

Hi Guys, it is extremely slo to load HTTPS pages, http work great, is there a fix or some special property we need to call to speed the load of a page?

Greg

Greg,

I don't see any difference in speed (using our Simple sample) when loading http or https site.

Does this happen on any site you try to load? Perhaps it's a server side issue (overloaded or something similiar).

You don't need to make any extra settings, when you do GET, wodHttpDLX will automatically adjust it self based on the http or https string found in the URL.

Regards,
Damba

Hi Damba, this is the code we are running to test it out

[code]
dim Http1
set Http1 = Server.CreateObject( WeOnlyDo.wodHttpDLXCom.1 )
Http1.Blocking = 1
Http1.URL = https://myr.trvlbooking.ca/edocs/defaultb2c.asp?lang=EN&alias=SQV&mytid=997163830
http1.Timeout = 30
Http1.GET

If http1.Response.StatusCode = 200 Then
Response.Write(Http1.Response.Body)
End If

Http1.Disconnect
Set Http1 = Nothing
[code]

could you please give it a try and let me know?, thanks for the feedback :)

Greg,

I get the same result for both requests (Http and Https). It takes less then a second to retrieve the page body.

I tested with our 1.Simple VB sample, and set Blocking to true.

I also changed the Command1_Click event to this:

[code]
Debug.Print Now
wodHttp1.Get txtURL.Text
Debug.Print Now
[/code]

Regards,
Damba

Greg,

I get the same result for both requests (Http and Https). It takes less then a second to retrieve the page body.

I tested with our 1.Simple VB sample, and set Blocking to true.

I also changed the Command1_Click event to this:

[code]
Debug.Print Now
wodHttp1.Get txtURL.Text
Debug.Print Now
[/code]

Regards,
Damba

Hi Damba, I've tried the VB example and yes it takes a sec or so :) it is great, when trying the ASP examples provided in the install it just delays like I am explaining, perhaps you can try it as well as see if you can replicate it?

Thank you for the quick responses.

Regards
Greg

Greg,

Nope, still the same. It takes about a second (a bit slower because of the page switching in explorer).

What version are you using? I've performed all the tests using the latest version available, and IE for browser.

Regards,
Damba

Greg,

Nope, still the same. It takes about a second (a bit slower because of the page switching in explorer).

What version are you using? I've performed all the tests using the latest version available, and IE for browser.

Regards,
Damba

Hi Damba, we just purchased the component like last week, was thast the latest one?

Greg,

Can you please check your Versio property? What does it return?

The latest version is 1.5.6.153.

Regards,
Damba

Greg,

Can you please check your Versio property? What does it return?

The latest version is 1.5.6.153.

Regards,
Damba

Hi Damba,
We did do check the version using code and see the same version number as you do.

The ASP page is running on https://myr.trvlbooking.ca.
The ASP page, via your com, is calling (scraping) a page on https://myr.trvlbooking.ca.
When we call a page within the same URL, via HTTPS, the delays are long. When calling a page within the same URL, via HTTP, response is immediate.

Greg,

I'd like to help, but I can't seem to duplicate this. I've performed more tests, even put a timestamp in the sample in order to see how long it takes forit to complete, but the request didn't take more then ~1 second to finish. The https requests are normally a bit slower because of the client-server negotiation, and encryption.

How long does it take you to complete a request?

Regards,
Damba

I have tried adding CertErrors, to assist in debugging... and and receive the following back:

[code]Unable to get issuer certificate locally. Certificate not trusted. Unable to verify the first certificate.[/code].

If I run the ASP script/com from another server (not running the myr.trvlbooking.ca domain), responses for HTTPS are instant.
When running the ASP script/com on the same server as the website being called in the COM (https only), the delay occurs (and the above error is encountered when certErrors is used).

Hope this helps to find the issue.

Regards,
Don

Hello,

The delay is upwards of 8-10 seconds.

Regards,
Don

Don,

Is client certificate needed to access that page from the same domain? If yes, did you install it on the machine and load it into wodHttpDLX?

Or perhaps it's not needed at all and you are setting it? In that case, try not use it.

Regards,
Damba

Hi Damba,

Really not sure what you mean...
If you goto the domain via HTTPS (even from the same server), all works and responds quickly.

However, only when your com is used from https://myr.trvlbooking.ca to a page on https://myr.trvlbooking.ca does the response get delayed and result in the error noted.

Is there possibly an issue in the com when calling the same website via HTTPS as the one the com is running on ? I only say this, because running the com from another server not running the myr.trvlbooking.ca domain (calling https://myr.trvlbooking.ca), it works.

Regards,
Don

Hi Damba,

A cert is installed on IIS for myr.trvlbooking.ca.
You can see this by going to https://myr.trvlbooking.ca.
The certificate is valid.

Do I need to load it into the com too, even though the webserver already has it ?

If so... how would I do this in ASP ?

Regards,
Don

Don,

That's Server certificate. That part should be ok. However, what permissions does your IIS account run as?

Can you please try assigning it Admin privileges just for a test? This should point us to the right direction in solving the issue. (You should be aware that this is a potential risk, so if you're doing it on live server, don't forget to restore the previous configuration).

In order to do that follow these steps:

Go to Start->Settings->Control Panel->Administrative Tools->Internet Services Manager. Find 'Default Web Site' here, right-click on it, select 'Properties'. Go to 'Directory Security' tab, at the top there is 'Anonymous access and authentication control' frame, and 'Edit' button. Click on 'Edit' button, and then on new 'Authentication Methods' dialog box select also 'Edit' button for 'Account used for anonymous access'.

Here you should enter Username: 'Administrator', and for Password: put administrator password. Click on 'Ok' to close all windows.

Regards,
Damba

Hi,

Ok... running the ASP page containing the com as administrator does immediately pull HTTPS.

I truly do not understand why the com woudl pull HTTP without issue, and only pull HTTPS with the error and slow response.

Is this something that can be fixed ?
or do we need ot run all our pages containing this com, as admin ?

Regards,
Don

Don,

That happens because IIS account doesn't have permissions to access Certificate stores as it's running with Guest permissions. However, we can make a workaround by exporting the certificates to a file, and passing it to wodHttpDLX directly.

Here are instructions how to do it:

http://www.weonlydo.com/HttpDLX/Help/index.html?page=wodHttpDLXLib~wodHttpDLX~LocalCertBag.html

I believe everything is explained there. Can you try it?

Regards,
Damba

Don,

I forgot to mention. Be sure that Guest account has permissions to access the file you create by exporting certificates.

Regards,
Damba

Hi Damba,

We removed admin rights on the file containing the COM code.
We have exported our certs to a file.
We have used LocalCertBag to load the certs file to the COM.
The error Unable to get issuer certificate locally. Certificate not trusted. Unable to verify the first certificate. is now longer received.

However, the delay when calling HTTPS pages is still occuring.

Any other thoughts ?

Regards,
Don

Hi Don,

I have try to duplicate your problem with delay but unfortunately didn't have luck. It takes only one second to get https://myr.trvlbooking.ca/ using wodHttpDLX and ASP.

Maybe you are somehow still using DEMO version.

Can you please download licensed version here and try it again:

http://www.weonlydo.com/index.asp?update=1

This is automated process. Make sure you use same email address that is registered with our system, one you used when you have purchased the product.

Let us know how it goes.

Regards,
Drazen

Hi Drazen,

We are using the licensed version (as the demo version does not recognize the LicenseKey option). We have also confirmed the version number prior. The licensed version was only downloaded and installed the other day.

To recap your testing...
1) You have a website under a domain (ie: test.com).
2) You have a cert installed under the test.com site.
3) You have an ASP page under the test.com site, using wodhttpdlx.
4) The wodhttpdlx COM is calling a page under the same domain test.com.
5) You call the ASP page via HTTPS.

We can duplicate this issue on 4 different servers, each with the same configuration.

Running the same ASP page from a different server, works perfectly.

Regards,
Don

Don,

I have try to follow your instruction but it works perfectly on my side. HTTPS page is open in one second.

Can you please zip and send us your ASP sample to techsupport@weonlydo.com

Which OS are you using? Which version of IIS and which browser are you testing on?

Can you maybe duplicate it with our wodWebServer ActiveX component? This is http and https server component.

You can download wodWebServer here:
http://www.weonlydo.com/Samples/wodWebServer.exe

You can run sample SamplesVBComponent3. SSL Server which can be found in wodWebServer Samples folder.

Drazen