OFFICIAL "SERVER PROBLEMS" THREAD

[Nick]

Originally Posted by S485122

No TLD (.org), how could your "speed-dial button" ever work ?

Jacob

Domain names used to be relative unless you put a dot at the end,
in the same way that directory path names are local unless you start with a /
Then this started causing problems with E-mail delivery,
and other problems with software written by people who did not know the rules.

[Prime95]

Originally Posted by James Heinrich

It makes perfect sense. There is a redirect rule (the kind that automatically changes mersenne.org -> www.mersenne.org, or http -> https) that is redirecting the home page to itself. A small typo, no doubt, easily done. I have brought it to George/Aaron's attention. They should have it fixed soon. Until then you can always go to another page (e.g. https://www.mersenne.org/primes/) and navigate from there.

Apparently I'm not man enough to figure out IIS redirection rules. Give me some hairy FFT code any day. Aaron will check in sooner or later.

[S485122]

Originally Posted by Prime95

Apparently I'm not man enough to figure out IIS redirection rules. Give me some hairy FFT code any day. Aaron will check in sooner or later.

I use the following in the .htaccess file at the root of my "site" :

RewriteEngine On
RewriteBase /
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Header set Strict-Transport-Security "max-age=60000; includeSubdomains; "
Options -Indexes

Jacob

[S485122]

Originally Posted by Nick

Domain names used to be relative unless you put a dot at the end,
in the same way that directory path names are local unless you start with a /
Then this started causing problems with E-mail delivery,
and other problems with software written by people who did not know the rules.

I think it is more a case of the browser not adding .com or .org to an incomplete address (the different browser.fixup.alternate.xxx setting in FF based browsers.) The rules you cite are for DNS resolving and configuration files, they would only work in the mersenne.org site if the querying device is in an .org TLD. For browsing, AFAIK, a FQDN is needed.

Jacob

[storm5510]

Originally Posted by James Heinrich

It makes perfect sense. There is a redirect rule (the kind that automatically changes mersenne.org -> www.mersenne.org, or http -> https) that is redirecting the home page to itself. A small typo, no doubt, easily done. I have brought it to George/Aaron's attention. They should have it fixed soon. Until then you can always go to another page (e.g. https://www.mersenne.org/primes/) and navigate from there.

The link is https://www.mersenne.org/ in my browser, on which, it was stalling. I try to avoid using shortened variations. If I had the fully qualified address, then there should have been no need to redirect. It is working properly now. Many thanks.

[storm5510]

It misdirected again, or whatever it does.

I appended the link: https://www.mersenne.org/manual_assignment/ This works fine.

[James Heinrich]

Originally Posted by storm5510

It misdirected again, or whatever it does.

Yes, the problem is still unresolved. It's (apparently) beyond George's ken, and Aaron is traveling at the moment and won't be able to look at it until tonight/tomorrow.

[Syntony]

Originally Posted by storm5510

The link is https://www.mersenne.org/ in my browser, on which, it was stalling. /---/ It is working properly now. Many thanks.

I was finding that it seemed to fail to resolve rather randomly using Firefox 78.0.2. After upgrading to 79.0, the problem seems to have disappeared. Possibly a browser glitch? Does that chime with anyone else?


No, forget that, I just hadn't tried enough - still random apparently...



Tony

[Madpoo]

Originally Posted by James Heinrich

Yes, the problem is still unresolved. It's (apparently) beyond George's ken, and Aaron is traveling at the moment and won't be able to look at it until tonight/tomorrow.

I got it fixed - finally.

Unfortunately I was on a road trip when I saw this and didn't have my laptop handy so it juts had to wait.

It was a little cut-and-paste issue with some new URL rewrite rules that had to do with the new CERT work type. Turns out IIS is picky about the order in which some conditions appear, for reasons unknown.

All better now.

[storm5510]

Originally Posted by Madpoo

I got it fixed - finally.

Unfortunately I was on a road trip when I saw this and didn't have my laptop handy so it juts had to wait.

It was a little cut-and-paste issue with some new URL rewrite rules that had to do with the new CERT work type. Turns out IIS is picky about the order in which some conditions appear, for reasons unknown.

All better now.

Other than recognizing an IP address, internet protocols is something I know virtually nothing about. Thank you!

[James Heinrich]

Originally Posted by storm5510

Other than recognizing an IP address

Even sticking with IPv4 you might not even always recognize an IP address, like http://2899904110 or http://0xACD9066E
(both are alternate representations of 172.217.6.110 = google.com)