The lawfirm site I just “finished” is hosted by Godaddy…
we have an ssl certificate on file. Per godaddy there is something in
freeway that I have to check to reroute the site from:
http;// www.buffalofamilylaw.com
to
https://wwww.buffalofamilylaw.com
I did see the thread abou tthe thank you / error page -
but I need the whole site redirected.
Thank you again and again
Julie
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Not sure what the “something” in Freeway might be…But couldn’t you just use a meta redirect/refresh tag?
<META HTTP-EQUIV="Refresh" CONTENT="0; URL=https://buffalofamilylaw.com">
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
What particularly do you need to protect?
The reason I ask is that usually there is a section that would come under the secure server but that may only be a couple of pages and doesn’t require a complete redirect.
What is the plan?
David
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
As I was told, per NYS or Erie County law any attorneys website needs
to be SSL. In addition it needs the bottom statement (attorney
advertising)
Per Godaddy I need to do some switch in freeway to have it redirect.
to the https://
they do not do anything. I also am waiting for the html to put the
“seal” on the site… which is another question - how do I do that…
but, I am more worried about redirecting.
Julie
On Nov 10, 2009, at 8:23 PM, DeltaDave wrote:
What particularly do you need to protect?
The reason I ask is that usually there is a section that would come
under the secure server but that may only be a couple of pages and
doesn’t require a complete redirect.What is the plan?
David
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Remember the list of sites I posted on 6th November under sitereview - none of those were https hosted!
I think I would be asking a few more questions about this because if you are limiting this site to publicly available information I cannot understand the requirement for a secure server.
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I did I was pleasantly surprised where they were from… (I am from
Jersey originally)
It might be an erie county thing also.
But I will “forward” your question to him. I thought it was strange…
Julie
On Nov 10, 2009, at 8:44 PM, DeltaDave wrote:
Remember the list of sites I posted on 6th November under sitereview
- none of those were https hosted!
I think I would be asking a few more questions about this because if
you are limiting this site to publicly available information I
cannot understand the requirement for a secure server.D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Does GoDaddy host https and http out of the same server folder? If they don’t (and it would be extremely odd if they did) then you can redirect the entire domain from non-secure to secure with a single .htaccess file.
Redirect 301 / https://your.domain.com/
Put that in a text file, name it .htaccess (you’ll have to do that part on the server) and Bob’s your uncle. With that file in your httpdocs folder, and all your site files in the httpsdocs folder, the entire site will be served out of the secure folder, even if it wasn’t requested from there.
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
great - now to upload to that folder in freeway - do I need to change
anything/? I will also contact godaddy how to redirect to the
httpsfolder?
I hate to ask… bobs your uncle? huh??
J
On Nov 10, 2009, at 8:57 PM, waltd wrote:
Does GoDaddy host https and http out of the same server folder? If
they don’t (and it would be extremely odd if they did) then you can
redirect the entire domain from non-secure to secure with a
single .htaccess file.Redirect 301 / https://your.domain.com/Put that in a text file, name it .htaccess (you’ll have to do that
part on the server) and Bob’s your uncle. With that file in your
httpdocs folder, and all your site files in the httpsdocs folder,
the entire site will be served out of the secure folder, even if it
wasn’t requested from there.Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Bob is that friend of your Mother’s that only appears when your Dad is away.
D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
thats what I thought… LOL but just checkn…
On Nov 10, 2009, at 9:13 PM, DeltaDave wrote:
Bob is that friend of your Mother’s that only appears when your Dad
is away.D
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Use an FTP application to look at your GoDaddy account folder. You will almost always be able to see at least one “level” above the folder where you put your files. So if there are two folders that are named similarly, like httpdocs and httpsdocs (that’s what Rackspace calls them) then by deduction you can figure out which one serves the secure site and which one does not. So in Freeway, you would change the Directory setting in the Upload dialog to match the path to the secure folder.
As for Bob, Google is your friend:
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Thank you for that… Ok… I will go investigate…
and thanks for the article… I thought something like dave explained…
and this…too… Had a feeling it was a british saying… 
J
On Nov 10, 2009, at 9:22 PM, waltd wrote:
Use an FTP application to look at your GoDaddy account folder. You
will almost always be able to see at least one “level” above the
folder where you put your files. So if there are two folders that
are named similarly, like httpdocs and httpsdocs (that’s what
Rackspace calls them) then by deduction you can figure out which one
serves the secure site and which one does not. So in Freeway, you
would change the Directory setting in the Upload dialog to match the
path to the secure folder.As for Bob, Google is your friend:
World Wide Words: Bob’s your uncle
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
If you google Erie, NY law firms, you find that none of the firms are using a secure site so something doesn’t seem right.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Just FYI., there is no Erie ny.
I totally agree w you all. O will check w him in the am
Thank you so much for your input
J
Sent from my iPhone
On Nov 10, 2009, at 23:23, Bryan Irvine email@hidden wrote:
If you google Erie, NY law firms, you find that none of the firms
are using a secure site so something doesn’t seem right.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 11 Nov 2009, 1:13 am, DeltaDave wrote:
Bob is that friend of your Mother’s that only appears when your Dad is away.
… and, in a distant past, delivered the milk too.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Here is the answer from godaddy… any thoughts on this would be great…
walter
there are no folders because it is a shared server and I can not do
what you recommended…
Do the page names (atttorneyprofile.html) do those have to be changed
sigh… always a learning experience…
J
On Nov 10, 2009, at 8:57 PM, waltd wrote:
Does GoDaddy host https and http out of the same server folder? If
they don’t (and it would be extremely odd if they did) then you can
redirect the entire domain from non-secure to secure with a
single .htaccess file.Redirect 301 / https://your.domain.com/Put that in a text file, name it .htaccess (you’ll have to do that
part on the server) and Bob’s your uncle. With that file in your
httpdocs folder, and all your site files in the httpsdocs folder,
the entire site will be served out of the secure folder, even if it
wasn’t requested from there.Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Hrm. That’s a careful non-answer you have there. A shared server has nothing at all to do with where they define your secure web root to be. You will not need to change anything about your site if the following works, a relative link will always work because it relates to the page that was sending it on to the next page.
TRY this (I have my doubts it will work on GD, but baby steps, right?):
Edit your .htaccess file to read thusly:
RewriteEngine On
RewriteCond %{SERVER_PORT} !^443$
RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R,L]
What this does is check every request made of the server to see if it came in under the secure port (443) rather than the normal 80. If it did, nothing happens. If it did not, the server makes a full external redirect to the requested URL under the https:// protocol. You won’t need to change anything at all about your site if this file (named .htaccess) is present in your site folder (and GoDaddy isn’t acting capriciously, which has been my sad experience there on many occasions).
If this is going to fail, it will fail spectacularly, as in Error 500, no pages are displayed ever. If that’s the case, delete the .htaccess file and try to convince your client to move to a provider that isn’t so odd, or to give up this idea that the pages have to be sent securely.
I frankly find that “requirement” to be extremely strange, bordering on someone playing a game of telephone here, where someone said one thing and it came out different on the other end. What I imagine is true is that any FORMS need to be sent under SSL protection, so as to dissuade wiretapping of privileged client-attorney communication. But to say that all PAGES need to be sent to the great wide open Internet under SSL protection is quite ridiculous.
Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Spectacular…
I made the .htaccess file
saved it as: .htaccess
put in it:
RewriteEngine On RewriteCond %{SERVER_PORT} !^443$ RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R,L]
w the sqiggles ( if these are not needed… let me know)
and got:
Internal Server Error
The server encountered an internal error or misconfiguration and was
unable to complete your request.
Please contact the server administrator, email@hidden
and inform them of the time the error occurred, and anything you might
have done that may have caused the error.
More information about this error may be available in the server error
log.
Thank you… so…
On Nov 11, 2009, at 11:32 AM, waltd wrote:
Hrm. That’s a careful non-answer you have there. A shared server has
nothing at all to do with where they define your secure web root to
be. You will not need to change anything about your site if the
following works, a relative link will always work because it relates
to the page that was sending it on to the next page.TRY this (I have my doubts it will work on GD, but baby steps,
right?):Edit your .htaccess file to read thusly:
RewriteEngine On RewriteCond %{SERVER_PORT} !^443$ RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R,L]What this does is check every request made of the server to see if
it came in under the secure port (443) rather than the normal 80. If
it did, nothing happens. If it did not, the server makes a full
external redirect to the requested URL under the https:// protocol.
You won’t need to change anything at all about your site if this
file (named .htaccess) is present in your site folder (and GoDaddy
isn’t acting capriciously, which has been my sad experience there on
many occasions).If this is going to fail, it will fail spectacularly, as in Error
500, no pages are displayed ever. If that’s the case, delete
the .htaccess file and try to convince your client to move to a
provider that isn’t so odd, or to give up this idea that the pages
have to be sent securely.I frankly find that “requirement” to be extremely strange, bordering
on someone playing a game of telephone here, where someone said one
thing and it came out different on the other end. What I imagine is
true is that any FORMS need to be sent under SSL protection, so as
to dissuade wiretapping of privileged client-attorney communication.
But to say that all PAGES need to be sent to the great wide open
Internet under SSL protection is quite ridiculous.Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Walt,
I took the squiggles out and it worked like a charm
you rock!
http://www.buffalofamilylaw.com
Here is my secondary question…
where do I put the html code so I have symbol at the bottom of the page?
J
On Nov 11, 2009, at 11:32 AM, waltd wrote:
Hrm. That’s a careful non-answer you have there. A shared server has
nothing at all to do with where they define your secure web root to
be. You will not need to change anything about your site if the
following works, a relative link will always work because it relates
to the page that was sending it on to the next page.TRY this (I have my doubts it will work on GD, but baby steps,
right?):Edit your .htaccess file to read thusly:
RewriteEngine On RewriteCond %{SERVER_PORT} !^443$ RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R,L]What this does is check every request made of the server to see if
it came in under the secure port (443) rather than the normal 80. If
it did, nothing happens. If it did not, the server makes a full
external redirect to the requested URL under the https:// protocol.
You won’t need to change anything at all about your site if this
file (named .htaccess) is present in your site folder (and GoDaddy
isn’t acting capriciously, which has been my sad experience there on
many occasions).If this is going to fail, it will fail spectacularly, as in Error
500, no pages are displayed ever. If that’s the case, delete
the .htaccess file and try to convince your client to move to a
provider that isn’t so odd, or to give up this idea that the pages
have to be sent securely.I frankly find that “requirement” to be extremely strange, bordering
on someone playing a game of telephone here, where someone said one
thing and it came out different on the other end. What I imagine is
true is that any FORMS need to be sent under SSL protection, so as
to dissuade wiretapping of privileged client-attorney communication.
But to say that all PAGES need to be sent to the great wide open
Internet under SSL protection is quite ridiculous.Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
No squiggles. They are there to render the code in the Web forum.
Walter
On Nov 11, 2009, at 11:48 AM, julie maxwell allen wrote:
Spectacular…
I made the .htaccess file
saved it as: .htaccessput in it:
RewriteEngine On RewriteCond %{SERVER_PORT} !^443$ RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R,L]w the sqiggles ( if these are not needed… let me know)
and got:
Internal Server ErrorThe server encountered an internal error or misconfiguration and was
unable to complete your request.
Please contact the server administrator, email@hidden
and inform them of the time the error occurred, and anything you
might have done that may have caused the error.More information about this error may be available in the server
error log.Thank you… so…
On Nov 11, 2009, at 11:32 AM, waltd wrote:
Hrm. That’s a careful non-answer you have there. A shared server
has nothing at all to do with where they define your secure web
root to be. You will not need to change anything about your site if
the following works, a relative link will always work because it
relates to the page that was sending it on to the next page.TRY this (I have my doubts it will work on GD, but baby steps,
right?):Edit your .htaccess file to read thusly:
RewriteEngine On RewriteCond %{SERVER_PORT} !^443$ RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R,L]What this does is check every request made of the server to see if
it came in under the secure port (443) rather than the normal 80.
If it did, nothing happens. If it did not, the server makes a full
external redirect to the requested URL under the https:// protocol.
You won’t need to change anything at all about your site if this
file (named .htaccess) is present in your site folder (and GoDaddy
isn’t acting capriciously, which has been my sad experience there
on many occasions).If this is going to fail, it will fail spectacularly, as in Error
500, no pages are displayed ever. If that’s the case, delete
the .htaccess file and try to convince your client to move to a
provider that isn’t so odd, or to give up this idea that the pages
have to be sent securely.I frankly find that “requirement” to be extremely strange,
bordering on someone playing a game of telephone here, where
someone said one thing and it came out different on the other end.
What I imagine is true is that any FORMS need to be sent under SSL
protection, so as to dissuade wiretapping of privileged client-
attorney communication. But to say that all PAGES need to be sent
to the great wide open Internet under SSL protection is quite
ridiculous.Walter
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options