Problems with .htaccess file

R

Robert Baer

Guest
My site works well now, with the .htaccess file disabled.
I edited it and commented out all of the lines that redirect HTTP to
HTTPS, and oil4lessllc.com to www.oil4lessllc.com and all variants i
collected.

Re-enabling it makes my site unaccesable, and i get repetitive
"calls", like
https://www.oil4lessllc.com/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/
Until something gets filled or otherwise runs out of steam.

And i have no clue as to what is messing up.

AFAIK there are no debuggers or tracers or other helpful
programs/adders/overlays etc.

Ideas?
Thanks.
 
On 2020-02-12, Robert Baer <robertbaer@localnet.com> wrote:
My site works well now, with the .htaccess file disabled.
I edited it and commented out all of the lines that redirect HTTP to
HTTPS, and oil4lessllc.com to www.oil4lessllc.com and all variants i
collected.

Re-enabling it makes my site unaccesable, and i get repetitive
"calls", like
https://www.oil4lessllc.com/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/
Until something gets filled or otherwise runs out of steam.

And i have no clue as to what is messing up.

AFAIK there are no debuggers or tracers or other helpful
programs/adders/overlays etc.

Ideas?
Thanks.

set a different document root for http and https

leave index.html out of the redirect


--
Jasen.
 
On 2020-02-12 08:00, Robert Baer wrote:
  My site works well now, with the .htaccess file disabled.
  I edited it and commented out all of the lines that redirect HTTP to
HTTPS, and oil4lessllc.com to www.oil4lessllc.com and all variants i
collected.

  Re-enabling it makes my site unaccesable, and i get repetitive
"calls", like
https://www.oil4lessllc.com/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/

 Until something gets filled or otherwise runs out of steam.

  And i have no clue as to what is messing up.

  AFAIK there are no debuggers or tracers or other helpful
programs/adders/overlays etc.

  Ideas?
  Thanks.

I had some similar trouble for a while, and no clue what was
wrong either. I finally realized that a mixture of http and
https with absolute URLs doesn't work anymore. Use relative
URLs wherever you can.

Jeroen Belleman
 
On 2/12/20 12:00 AM, Robert Baer wrote:
>   And i have no clue as to what is messing up.

Do you have a backup of a working version that you can compare to?

  AFAIK there are no debuggers or tracers or other helpful
programs/adders/overlays etc.

Are you running Apache (I've not looked at headers) or something else
that uses the .htaccess file?

>   Ideas?

Presuming that you're running Apche HTTPD. — My guess, is that you're
missing some RewriteCond statements to only apply the RewriteRule(s) to
the proper requests.

It looks like you've likely got a recursive loop.

Email me directly if you'd like to discuss this further. (I don't feel
like this is sci.electronics.design related.)

>   Thanks.

Good luck.



--
Grant. . . .
unix || die
 
Jasen Betts wrote:
On 2020-02-12, Robert Baer <robertbaer@localnet.com> wrote:
My site works well now, with the .htaccess file disabled.
I edited it and commented out all of the lines that redirect HTTP to
HTTPS, and oil4lessllc.com to www.oil4lessllc.com and all variants i
collected.

Re-enabling it makes my site unaccesable, and i get repetitive
"calls", like
https://www.oil4lessllc.com/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/
Until something gets filled or otherwise runs out of steam.

And i have no clue as to what is messing up.

AFAIK there are no debuggers or tracers or other helpful
programs/adders/overlays etc.

Ideas?
Thanks.

set a different document root for http and https

leave index.html out of the redirect


Cannot work as-is; HTTP is re-directed to HTPPS elsewhere.
 
Jeroen Belleman wrote:
On 2020-02-12 08:00, Robert Baer wrote:
   My site works well now, with the .htaccess file disabled.
   I edited it and commented out all of the lines that redirect HTTP
to HTTPS, and oil4lessllc.com to www.oil4lessllc.com and all variants
i collected.

   Re-enabling it makes my site unaccesable, and i get repetitive
"calls", like
https://www.oil4lessllc.com/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/

  Until something gets filled or otherwise runs out of steam.

   And i have no clue as to what is messing up.

   AFAIK there are no debuggers or tracers or other helpful
programs/adders/overlays etc.

   Ideas?
   Thanks.

I had some similar trouble for a while, and no clue what was
wrong either. I finally realized that a mixture of http and
https with absolute URLs doesn't work anymore. Use relative
URLs wherever you can.

Jeroen Belleman
Yes; that is what i do.
But what i need is either a reasonable way to find out what is wrong
with my .htaccess file (and fix it),or some expert to fix it.

Thanks.
 
Grant Taylor wrote:
On 2/12/20 12:00 AM, Robert Baer wrote:
   And i have no clue as to what is messing up.

Do you have a backup of a working version that you can compare to?
* I have learned the hard way to have backup versions.
But i also know i never had a working version.

   AFAIK there are no debuggers or tracers or other helpful
programs/adders/overlays etc.

Are you running Apache (I've not looked at headers) or something else
that uses the .htaccess file?
* Yes; Apache.

   Ideas?

Presuming that you're running Apche HTTPD.  —  My guess, is that you're
missing some RewriteCond statements to only apply the RewriteRule(s) to
the proper requests.
* That may be if and when i can get to the point where the .htaccess
file works at all.
Right now,i have all of that stuff commented out and the file does
not work.
Seems to prevent CSS to do anything; cannot say about JavaScript.


It looks like you've likely got a recursive loop.

Email me directly if you'd like to discuss this further.  (I don't feel
like this is sci.electronics.design related.)
* Correct, but there are so many people here that know so many other
things, and i am in a pickle; that is the why of the posting.

   Thanks.

Good luck.



Thanks.
 
On Wednesday, February 12, 2020 at 4:20:43 PM UTC-5, Robert Baer wrote:
Grant Taylor wrote:
On 2/12/20 12:00 AM, Robert Baer wrote:
   And i have no clue as to what is messing up.

Do you have a backup of a working version that you can compare to?
* I have learned the hard way to have backup versions.
But i also know i never had a working version.


   AFAIK there are no debuggers or tracers or other helpful
programs/adders/overlays etc.

Are you running Apache (I've not looked at headers) or something else
that uses the .htaccess file?
* Yes; Apache.


   Ideas?

Presuming that you're running Apche HTTPD.  —  My guess, is that you're
missing some RewriteCond statements to only apply the RewriteRule(s) to
the proper requests.
* That may be if and when i can get to the point where the .htaccess
file works at all.
Right now,i have all of that stuff commented out and the file does
not work.
Seems to prevent CSS to do anything; cannot say about JavaScript.



It looks like you've likely got a recursive loop.

Email me directly if you'd like to discuss this further.  (I don't feel
like this is sci.electronics.design related.)
* Correct, but there are so many people here that know so many other
things, and i am in a pickle; that is the why of the posting.

Who hosts the website? Ask them for help.
 
On 2020-02-12, Robert Baer <robertbaer@localnet.com> wrote:
Jasen Betts wrote:
On 2020-02-12, Robert Baer <robertbaer@localnet.com> wrote:
My site works well now, with the .htaccess file disabled.
I edited it and commented out all of the lines that redirect HTTP to
HTTPS, and oil4lessllc.com to www.oil4lessllc.com and all variants i
collected.

Re-enabling it makes my site unaccesable, and i get repetitive
"calls", like
https://www.oil4lessllc.com/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/
Until something gets filled or otherwise runs out of steam.

And i have no clue as to what is messing up.

AFAIK there are no debuggers or tracers or other helpful
programs/adders/overlays etc.

Ideas?
Thanks.

set a different document root for http and https

leave index.html out of the redirect


Cannot work as-is; HTTP is re-directed to HTPPS elsewhere.

That cannot be correct.

--
Jasen.
 
Jasen Betts wrote:
On 2020-02-12, Robert Baer <robertbaer@localnet.com> wrote:
Jasen Betts wrote:
On 2020-02-12, Robert Baer <robertbaer@localnet.com> wrote:
My site works well now, with the .htaccess file disabled.
I edited it and commented out all of the lines that redirect HTTP to
HTTPS, and oil4lessllc.com to www.oil4lessllc.com and all variants i
collected.

Re-enabling it makes my site unaccesable, and i get repetitive
"calls", like
https://www.oil4lessllc.com/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/
Until something gets filled or otherwise runs out of steam.

And i have no clue as to what is messing up.

AFAIK there are no debuggers or tracers or other helpful
programs/adders/overlays etc.

Ideas?
Thanks.

set a different document root for http and https

leave index.html out of the redirect


Cannot work as-is; HTTP is re-directed to HTPPS elsewhere.

That cannot be correct.

Typo; HTTP re-directed to HTTPS elsewhere.
 
Robert Baer wrote:
Jasen Betts wrote:
On 2020-02-12, Robert Baer <robertbaer@localnet.com> wrote:
Jasen Betts wrote:
On 2020-02-12, Robert Baer <robertbaer@localnet.com> wrote:
     My site works well now, with the .htaccess file disabled.
     I edited it and commented out all of the lines that redirect
HTTP to
HTTPS, and oil4lessllc.com to www.oil4lessllc.com and all variants i
collected.

     Re-enabling it makes my site unaccesable, and i get repetitive
"calls", like
https://www.oil4lessllc.com/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/index.html/

    Until something gets filled or otherwise runs out of steam.

     And i have no clue as to what is messing up.

     AFAIK there are no debuggers or tracers or other helpful
programs/adders/overlays etc.

     Ideas?
     Thanks.

set a different document root for http and https

leave index.html out of the redirect


    Cannot work as-is; HTTP is re-directed to HTPPS elsewhere.

That cannot be correct.

  Typo; HTTP re-directed to HTTPS elsewhere.
I have chopped the .htaccess file so only the first 267 lines exist,
and that works.
 
On Thu, 13 Feb 2020 23:49:53 -0800, Robert Baer
<robertbaer@localnet.com> wrote:

set a different document root for http and https

leave index.html out of the redirect


    Cannot work as-is; HTTP is re-directed to HTPPS elsewhere.

That cannot be correct.

Disclaimer: I know just about as little about HTML(S) as is possible.

My site, neon-john.com, was composed (not programmed) in plain old
HTML. My ISP, dreamhost.com, has joined the "let's encrypt| "
movement. That involves registering an HTTPS domain name,
generating a new key each month and automatically installing it on the
host. The idea of "Let's Encrypt|" is to make it more difficult for
TLAs and corporate snooper to spy on a connection to a user.

I have no idea what kind of PFM goes on at the host but I do know that
I can edit my site and both HTML and HTMLS show up at almost the same
time in seconds.

This a job that I'd not give a second thought to farming out. Oh, did
I mention that Dreamhost's services for this task are free.

John
John DeArmond
http://www.neon-john.com
http://www.tnduction.com
Tellico Plains, Occupied TN
See website for email address
 
Neon John wrote:
> Robert Baer wrote:

<snip>

I have chopped the .htaccess file so only the first 267 lines
exist, and that works.

Disclaimer: I know just about as little about HTML(S) as is possible.

My site, neon-john.com, was composed (not programmed) in plain old
HTML. My ISP, dreamhost.com, has joined the "let's encrypt| "
movement. That involves registering an HTTPS domain name,
generating a new key each month and automatically installing it on the
host. The idea of "Let's Encrypt|" is to make it more difficult for
TLAs and corporate snooper to spy on a connection to a user.

I have no idea what kind of PFM goes on at the host but I do know that
I can edit my site and both HTML and HTMLS show up at almost the same
time in seconds.

This a job that I'd not give a second thought to farming out. Oh, did
I mention that Dreamhost's services for this task are free.

Robert, your thread captivated me from the start. Regretfully, my
impulse to suggest that you simply whittle your .htaccess file down
wasn't shared because it wasn't nearly as "sexy" as the silver bullets
offered by others. My own .htaccess file for https://crcomp.net contains
a grand total of 9 lines. So, whatever's going on in your .htaccess file
is a little out of my league.

John, Let's Encrypt [1] also caught my eye a while ago. QTH [2] is
listed as one of the fully automatic Let's Encrypt providers. [3] QTH is
also a ham radio prosign. It's a shame that it took me so long to hook
up with a provider that's head and shoulders above the rest. QTH
provides all of the unix (BSD) goodies that don't even begin to register
with the typical Microsoft centric hosting vendor.

Note.

[1] https://letsencrypt.org/
[2] https://hosting.qth.com/
[3] https://community.letsencrypt.org/t/web-hosting-who-support-lets-encrypt/6920#full

Thank you,

--
Don Kuenz KB7RPU
There was a young lady named Bright Whose speed was far faster than light;
She set out one day In a relative way And returned on the previous night.
 
Neon John wrote:
On Thu, 13 Feb 2020 23:49:53 -0800, Robert Baer
robertbaer@localnet.com> wrote:

set a different document root for http and https

leave index.html out of the redirect


    Cannot work as-is; HTTP is re-directed to HTPPS elsewhere.

That cannot be correct.

Disclaimer: I know just about as little about HTML(S) as is possible.

My site, neon-john.com, was composed (not programmed) in plain old
HTML. My ISP, dreamhost.com, has joined the "let's encrypt| "
movement. That involves registering an HTTPS domain name,
generating a new key each month and automatically installing it on the
host. The idea of "Let's Encrypt|" is to make it more difficult for
TLAs and corporate snooper to spy on a connection to a user.

I have no idea what kind of PFM goes on at the host but I do know that
I can edit my site and both HTML and HTMLS show up at almost the same
time in seconds.

This a job that I'd not give a second thought to farming out. Oh, did
I mention that Dreamhost's services for this task are free.

John
John DeArmond
http://www.neon-john.com
http://www.tnduction.com
Tellico Plains, Occupied TN
See website for email address
Thanks!
If i get nowhere, i will ask them for help.
 
Don Kuenz wrote:
Neon John wrote:
Robert Baer wrote:

snip

I have chopped the .htaccess file so only the first 267 lines
exist, and that works.

Disclaimer: I know just about as little about HTML(S) as is possible.

My site, neon-john.com, was composed (not programmed) in plain old
HTML. My ISP, dreamhost.com, has joined the "let's encrypt| "
movement. That involves registering an HTTPS domain name,
generating a new key each month and automatically installing it on the
host. The idea of "Let's Encrypt|" is to make it more difficult for
TLAs and corporate snooper to spy on a connection to a user.

I have no idea what kind of PFM goes on at the host but I do know that
I can edit my site and both HTML and HTMLS show up at almost the same
time in seconds.

This a job that I'd not give a second thought to farming out. Oh, did
I mention that Dreamhost's services for this task are free.

Robert, your thread captivated me from the start. Regretfully, my
impulse to suggest that you simply whittle your .htaccess file down
wasn't shared because it wasn't nearly as "sexy" as the silver bullets
offered by others. My own .htaccess file for https://crcomp.net contains
a grand total of 9 lines. So, whatever's going on in your .htaccess file
is a little out of my league.

John, Let's Encrypt [1] also caught my eye a while ago. QTH [2] is
listed as one of the fully automatic Let's Encrypt providers. [3] QTH is
also a ham radio prosign. It's a shame that it took me so long to hook
up with a provider that's head and shoulders above the rest. QTH
provides all of the unix (BSD) goodies that don't even begin to register
with the typical Microsoft centric hosting vendor.

Note.

[1] https://letsencrypt.org/
[2] https://hosting.qth.com/
[3] https://community.letsencrypt.org/t/web-hosting-who-support-lets-encrypt/6920#full

Thank you,

Thanks.
 
Robert Baer wrote:
Don Kuenz wrote:
Neon John wrote:
  Robert Baer wrote:

snip

   I have chopped the .htaccess file so only the first 267 lines
   exist, and that works.

Disclaimer: I know just about as little about HTML(S) as is possible.

My site, neon-john.com, was composed (not programmed) in plain old
HTML.  My ISP, dreamhost.com, has joined the "let's encrypt| "
movement.  That involves  registering an HTTPS  domain name,
generating a new key each month and automatically installing it on the
host. The idea of "Let's Encrypt|" is to make it more difficult for
TLAs and corporate snooper to spy on a connection to a user.

I have no idea what kind of PFM goes on at the host but I do know that
I can edit my site and both HTML and HTMLS show up at almost the same
time in seconds.

This a job that I'd not give a second thought to farming out.  Oh, did
I mention that Dreamhost's services  for this task are free.

Robert, your thread captivated me from the start. Regretfully, my
impulse to suggest that you simply whittle your .htaccess file down
wasn't shared because it wasn't nearly as "sexy" as the silver bullets
offered by others. My own .htaccess file for https://crcomp.net contains
a grand total of 9 lines. So, whatever's going on in your .htaccess file
is a little out of my league.

John, Let's Encrypt [1] also caught my eye a while ago. QTH [2] is
listed as one of the fully automatic Let's Encrypt providers. [3] QTH is
also a ham radio prosign. It's a shame that it took me so long to hook
up with a provider that's head and shoulders above the rest. QTH
provides all of the unix (BSD) goodies that don't even begin to register
with the typical Microsoft centric hosting vendor.
Note.

[1] https://letsencrypt.org/
[2] https://hosting.qth.com/
[3]
https://community.letsencrypt.org/t/web-hosting-who-support-lets-encrypt/6920#full


Thank you,

  Thanks.
Called Godaddy; they said my SEO redirects were conflicting with
others and that i did not need all of that other stuff.
They gave me a 4-liner that they use in the Cpanel:
## REDIRECT HTTP TO HTTPS AND NON-WWW VERSION TO WWW VERSION
# Copied from Godaddy : redirect to HTTPS
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteCond %{HTTP_HOST} ^(www\.)?oil4lessllc\.com
RewriteRule ^(.*)$ https://www.oil4lessllc.com/$1 [R,L]
# These 4 lines are all they have in Cpanel

Problems solved.
Thanks.
 
Robert Baer wrote:
Neon John wrote:
On Thu, 13 Feb 2020 23:49:53 -0800, Robert Baer
robertbaer@localnet.com> wrote:

set a different document root for http and https

leave index.html out of the redirect


     Cannot work as-is; HTTP is re-directed to HTPPS elsewhere.

That cannot be correct.

Disclaimer: I know just about as little about HTML(S) as is possible.

My site, neon-john.com, was composed (not programmed) in plain old
HTML.  My ISP, dreamhost.com, has joined the "let's encrypt| "
movement.  That involves  registering an HTTPS  domain name,
generating a new key each month and automatically installing it on the
host. The idea of "Let's Encrypt|" is to make it more difficult for
TLAs and corporate snooper to spy on a connection to a user.

I have no idea what kind of PFM goes on at the host but I do know that
I can edit my site and both HTML and HTMLS show up at almost the same
time in seconds.

This a job that I'd not give a second thought to farming out.  Oh, did
I mention that Dreamhost's services  for this task are free.

John
John DeArmond
http://www.neon-john.com
http://www.tnduction.com
Tellico Plains, Occupied TN
See website for email address

  Thanks!
  If i get nowhere, i will ask them for help.
Called Godaddy; they said my SEO redirects were conflicting with
others and that i did not need all of that other stuff.
They gave me a 4-liner that they use in the Cpanel:
## REDIRECT HTTP TO HTTPS AND NON-WWW VERSION TO WWW VERSION
# Copied from Godaddy : redirect to HTTPS
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteCond %{HTTP_HOST} ^(www\.)?oil4lessllc\.com
RewriteRule ^(.*)$ https://www.oil4lessllc.com/$1 [R,L]
# These 4 lines are all they have in Cpanel

Problems solved.
Thanks.
 
On Sunday, February 16, 2020 at 10:28:08 PM UTC-5, Robert Baer wrote:
Called Godaddy; they said my SEO redirects were conflicting with
others and that i did not need all of that other stuff.
They gave me a 4-liner that they use in the Cpanel:
## REDIRECT HTTP TO HTTPS AND NON-WWW VERSION TO WWW VERSION
# Copied from Godaddy : redirect to HTTPS
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteCond %{HTTP_HOST} ^(www\.)?oil4lessllc\.com
RewriteRule ^(.*)$ https://www.oil4lessllc.com/$1 [R,L]
# These 4 lines are all they have in Cpanel

Problems solved.
Thanks.

Once again, you ignored me, but ended up doing as I suggested. From my post on Feb 12th:

Who hosts the website? Ask them for help.
 

Welcome to EDABoard.com

Sponsor

Back
Top