by Dart Communications - Product Type: Component / ActiveX OCX / ActiveX DLL / DLL
Hi,
I have a problem to solve and was wondering if any of your tools could help me.
The problem:
I have a website which when a user navigates to show a Login page.
The user jeys in his username & password and if he is a valid user another page with a button "Upload" is displayed.
When he clicks on this button a page through which he can upload a file is displayed.
The user can select the file and upload it.
What do i want:
I want all this to be automated. I will hardcode the username & password and the file to upload.
And all the steps mentioned above are to be done without user intervention. The program will be automatically executed at a predefined time. And do all the stuff without showing a single HTML page.
Note: I cannot make any changes to the site at the server.
Regards,
Rajiv
Reply
Does the PowerTCP tool require a minimum version if Internet Explorer for HTTP and HTTPS transmission?
Reply
RE: PowerTCP Web Enterprise Tool - WinInet requ... Dart Tech Support 12-Jul-2001 09:47:30
The Web Enterprise is not dependent on wininet. However, there is still a minimum IE requirement (IE 4.01 or higher). For Win 95/98 machines, to use Https requires IE 5.01 with 128-bit encryption (plus some additional requirements). This is outlined in the help file.
Reply
Does this work with Windows 2000. I have a need to find a way to support SSL Wildcarding on Windows 2000 with IIS 5.0. This is a well-know issue with this configuration, as it USE TO work with NT and IIS 4.0, but not with IIS 5.0 under Win2K.
Reply
RE: PowerTCP Web Enterprise Tool Dart Tech Support 12-Jul-2001 09:46:42
Sorry, we do not know what "SSL Wildcarding" is. The Tool does work in Win 2000, though.
ReplyRE: PowerTCP Web Enterprise Tool jim [United Kingdom] 02-Nov-2001 09:26:24
A wildcard certificate is a certificate that can be used on multiple hosts. Such a certificate has a CommonName like *.domain.com. - when Netscape Navigator checks the host name in this certificate it uses a shell expansion procedure to see if it matches. In the example given, any host ending in .domain.com will be acceptable. MSIE does not implement wildcard certificate name checking. Wildcards seem to work with IE 4.0 and IE 5.0., but Microsoft officially disapproves of wildcards, so there can be no guarantee that wildcarding will work with any Microsoft product for any period of time.
P.S. I'm rather worried by the fact that a company that sells internet SSL components doesn't know about this type of certificate! I'm even more worried that they weren't concerned enough by their ignorance to bother looking it up!! Makes you wonder how much of that ignorance/laissez-faire has gone into their SSL component implementation...
Reply
Publisher
Primary Category
Related Products
Related Categories