FrontPage forms in HTTPS:// (Full Version)

All Forums >> [Web Development] >> Server Issues



Message

portside -> FrontPage forms in HTTPS:// (7/11/2007 18:27:12)

I have a GoDaddy Account and have been running a FrontPage email form in HTTPS:// for several years. Last month I received a notification from GoDaddy saying that they were changing me to a different server for maintenance issues. After the migration to the new server, my FrontPage email form no longer works in the HTTPS:// mode. It still works in the HTTP:// setting. I have exausted all avenues to try to figure out what the deal is. They suggested un-installing and re-installing FP extensions. I have done this 3 times now to no avale... Now they say that forms are not supported in the HTTPS:// enviroment. I say BS. It worked fine for several years until the server change. Can anyone shine any light on the subject, like any server issues, settings, ANYTHING. They suggested building a GDFORM.php. I know nothing about this stuff. Will my form ever work again in HTTPS:// ?? Please help. Thanks, Ken



coreybryant -> RE: FrontPage forms in HTTPS:// (7/12/2007 8:54:51)

Is the https on your own SSL or a shared SSL? Or also realize since this form is just being emailed to you that it is no longer secure?



portside -> RE: FrontPage forms in HTTPS:// (7/12/2007 13:22:43)

I do own the SSL, not shared. I think it is called the TURBO SSL from GoDaddy. I was under the understanding that since the form comes to me from linhostssl06.prod.mesa1.secureserver.net that it was secure. Am I wrong? Any help would be great. Thanks, Ken



coreybryant -> RE: FrontPage forms in HTTPS:// (7/12/2007 13:29:48)

It seems that it is a shared SSL. Let's say your domain is www.example.com and you direct users to https://www.example.com - that is your own SSL. If you need to direct users to https://example.secureserver.net or https://www.secureserver.net/example.com - that is an example of a shared SSL. The SSL cert is issued to secureserver.net and not www.example.com. Only if you own the domain secureserver.net basically would it be your

It might be secure on the site, but once they hit transmit and it gets converted to an email, it is not secure. The SSL cert basically secures the information being sent from the browser to the server. When that SSL cert is no longer involved, i.e. it being sent to you in a plain text email message, it is not secure.

Now, assuming that linhostssl06.prod.mesa1.secureserver.net is your secure site, then linhostssl06.prod.mesa1.secureserver.net needs to be a FP website so FPSE can process your form. Usually, this is somewhat difficult / tedious and most hosting companies don't support this because of the problems - they usually recommend your own SSL cert at least



portside -> RE: FrontPage forms in HTTPS:// (7/15/2007 14:03:10)

Hey Cory, thanks for your reply. I defenantly own the SSL cert as I can hyperlink to the page I need to be secure at https://www.portsidevacation.com/Vacation-Property-Agreement/Agreementform.htm

I assume that I own the certificate based on your message. I also understand your point about the security of the form mailer after you hit sumbit. I am currently working on a php form handler using a gdform.php script. I am a script writing neophite, so I plan to pay someone to duplicate the on-line form I currently have to a php script for reservation submissions. Let me know if you or anyone else you know would be interested. Thanks, Ken



coreybryant -> RE: FrontPage forms in HTTPS:// (7/15/2007 17:16:16)

Then it should work. Does your webhosting provider have a control panel where you can check FPSE? If so, you mght want to do that, and then on FP, go to Tools - Recalculate Hyperlinks, and publish

If Godaddy just copied your files and you did not publish them - this is where the problem lies. Those _vti folders need to be created by Frontpage / published by Frontpage to the server. If you copy them - this will cause more problems

Just keep in mind to have a complete secure email, you would need to use something like PGP



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
6.445313E-02