“Secure connection failed” SSL error on PHP script depending on the GET parameters?
up vote
0
down vote
favorite
I'm using Wordpress with forced HTTPS (at the wp-config.php level) and am having a strange problem with the https://mysite.example/wp-admin/admin.php url.
When viewing the theme's headers editor section at "https://mysite.example/wp-admin/admin.php?page=Headers", the SSL is successful. However, when another variable is added, i.e "https://mysite.example/wp-admin/admin.php?page=Headers&item_name=Site+Header&item_id=default_topbar__languages", the SSL connection fails on chrome and Firefox on multiple devices. Secure Connection Failed: The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
My first instinct would be that this shouldn't happen because the URL goes to the same file - which shouldn't have a chance to execute (changing the outcome) before the SSL connection is established.
The status bar loops between "Waiting for server", "Performing TLS handshake" and "looking up site".
Does anyone have any idea what could cause this kind of behavior on one specific page - only when the GET parameters are added? I've already tried checking the SSL certificate is valid (it is), and the .htaccess for any strange loops (there aren't).
Is my assumption that the parameters shouldn't affect anything because the script can't execute before SSL is established mistaken?
Thanks!
edit
This client is on shared hosting (Godaddy) so I can't see any vhosts or config files. However the .htaccess file is as follows:
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^index.php$ - [L]
# add a trailing slash to /wp-admin
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^ - [L]
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^(.*.php)$ $1 [L]
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule . index.php [L]
RewriteCond %{HTTP_HOST} ^my-site.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.my-site.com$
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^testing$ "http://my-site.com/" [R=301,L]
RewriteCond %{HTTP_HOST} ^my-site.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.my-site.com$
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^us$ "http://my-site.com/" [R=301,L]
RewriteCond %{HTTP_HOST} ^my-site.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.my-site.com$
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^us/ja/$ "https://my-site.com/ja/" [R=301,L]
php wordpress ssl https
asked Nov 12 at 6:41
Toby
1748
add a comment |
up vote
0
down vote
favorite
I'm using Wordpress with forced HTTPS (at the wp-config.php level) and am having a strange problem with the https://mysite.example/wp-admin/admin.php url.
When viewing the theme's headers editor section at "https://mysite.example/wp-admin/admin.php?page=Headers", the SSL is successful. However, when another variable is added, i.e "https://mysite.example/wp-admin/admin.php?page=Headers&item_name=Site+Header&item_id=default_topbar__languages", the SSL connection fails on chrome and Firefox on multiple devices. Secure Connection Failed: The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
My first instinct would be that this shouldn't happen because the URL goes to the same file - which shouldn't have a chance to execute (changing the outcome) before the SSL connection is established.
The status bar loops between "Waiting for server", "Performing TLS handshake" and "looking up site".
Does anyone have any idea what could cause this kind of behavior on one specific page - only when the GET parameters are added? I've already tried checking the SSL certificate is valid (it is), and the .htaccess for any strange loops (there aren't).
Is my assumption that the parameters shouldn't affect anything because the script can't execute before SSL is established mistaken?
Thanks!
edit
This client is on shared hosting (Godaddy) so I can't see any vhosts or config files. However the .htaccess file is as follows:
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^index.php$ - [L]
# add a trailing slash to /wp-admin
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^ - [L]
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^(.*.php)$ $1 [L]
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule . index.php [L]
RewriteCond %{HTTP_HOST} ^my-site.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.my-site.com$
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^testing$ "http://my-site.com/" [R=301,L]
RewriteCond %{HTTP_HOST} ^my-site.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.my-site.com$
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^us$ "http://my-site.com/" [R=301,L]
RewriteCond %{HTTP_HOST} ^my-site.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.my-site.com$
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^us/ja/$ "https://my-site.com/ja/" [R=301,L]
php wordpress ssl https
asked Nov 12 at 6:41
Toby
1748
1
The query string shouldn't affect this by default. However, since we have no idea what your vhost settings/htaccess looks like or if there is anything in your code that does something specific if those parameters are present, we can't even begin to guess.
– Magnus Eriksson
Nov 12 at 6:47
@MagnusEriksson Thanks for your reply. I attached my htaccess file, I don't see anything obvious that would cause this. We don't have access to the apache/vhosts/ssl config because this site is on a shared godaddy server which has proprietary tools you have to use to manage that. The certificate is checking out OK on all the SSL checker sites I've looked at though.
– Toby
Nov 12 at 6:52
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm using Wordpress with forced HTTPS (at the wp-config.php level) and am having a strange problem with the https://mysite.example/wp-admin/admin.php url.
When viewing the theme's headers editor section at "https://mysite.example/wp-admin/admin.php?page=Headers", the SSL is successful. However, when another variable is added, i.e "https://mysite.example/wp-admin/admin.php?page=Headers&item_name=Site+Header&item_id=default_topbar__languages", the SSL connection fails on chrome and Firefox on multiple devices. Secure Connection Failed: The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
My first instinct would be that this shouldn't happen because the URL goes to the same file - which shouldn't have a chance to execute (changing the outcome) before the SSL connection is established.
The status bar loops between "Waiting for server", "Performing TLS handshake" and "looking up site".
Does anyone have any idea what could cause this kind of behavior on one specific page - only when the GET parameters are added? I've already tried checking the SSL certificate is valid (it is), and the .htaccess for any strange loops (there aren't).
Is my assumption that the parameters shouldn't affect anything because the script can't execute before SSL is established mistaken?
Thanks!
edit
This client is on shared hosting (Godaddy) so I can't see any vhosts or config files. However the .htaccess file is as follows:
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^index.php$ - [L]
# add a trailing slash to /wp-admin
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^ - [L]
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^(.*.php)$ $1 [L]
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule . index.php [L]
RewriteCond %{HTTP_HOST} ^my-site.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.my-site.com$
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^testing$ "http://my-site.com/" [R=301,L]
RewriteCond %{HTTP_HOST} ^my-site.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.my-site.com$
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^us$ "http://my-site.com/" [R=301,L]
RewriteCond %{HTTP_HOST} ^my-site.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.my-site.com$
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^us/ja/$ "https://my-site.com/ja/" [R=301,L]
php wordpress ssl https
asked Nov 12 at 6:41
Toby
1748
I'm using Wordpress with forced HTTPS (at the wp-config.php level) and am having a strange problem with the https://mysite.example/wp-admin/admin.php url.
When viewing the theme's headers editor section at "https://mysite.example/wp-admin/admin.php?page=Headers", the SSL is successful. However, when another variable is added, i.e "https://mysite.example/wp-admin/admin.php?page=Headers&item_name=Site+Header&item_id=default_topbar__languages", the SSL connection fails on chrome and Firefox on multiple devices. Secure Connection Failed: The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
My first instinct would be that this shouldn't happen because the URL goes to the same file - which shouldn't have a chance to execute (changing the outcome) before the SSL connection is established.
The status bar loops between "Waiting for server", "Performing TLS handshake" and "looking up site".
Does anyone have any idea what could cause this kind of behavior on one specific page - only when the GET parameters are added? I've already tried checking the SSL certificate is valid (it is), and the .htaccess for any strange loops (there aren't).
Is my assumption that the parameters shouldn't affect anything because the script can't execute before SSL is established mistaken?
Thanks!
edit
This client is on shared hosting (Godaddy) so I can't see any vhosts or config files. However the .htaccess file is as follows:
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^index.php$ - [L]
# add a trailing slash to /wp-admin
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^ - [L]
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^(.*.php)$ $1 [L]
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule . index.php [L]
RewriteCond %{HTTP_HOST} ^my-site.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.my-site.com$
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^testing$ "http://my-site.com/" [R=301,L]
RewriteCond %{HTTP_HOST} ^my-site.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.my-site.com$
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^us$ "http://my-site.com/" [R=301,L]
RewriteCond %{HTTP_HOST} ^my-site.com$ [OR]
RewriteCond %{HTTP_HOST} ^www.my-site.com$
RewriteCond %{REQUEST_URI} !^/[0-9]+..+.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/.well-known/pki-validation/[A-F0-9]{32}.txt(?: Comodo DCV)?$
RewriteRule ^us/ja/$ "https://my-site.com/ja/" [R=301,L]
php wordpress ssl https
php wordpress ssl https
asked Nov 12 at 6:41
Toby
1748
asked Nov 12 at 6:41
Toby
1748
edited Nov 12 at 6:50
asked Nov 12 at 6:41
Toby
1748
asked Nov 12 at 6:41
Toby
1748
asked Nov 12 at 6:41
Toby
1748
1748
1
The query string shouldn't affect this by default. However, since we have no idea what your vhost settings/htaccess looks like or if there is anything in your code that does something specific if those parameters are present, we can't even begin to guess.
– Magnus Eriksson
Nov 12 at 6:47
@MagnusEriksson Thanks for your reply. I attached my htaccess file, I don't see anything obvious that would cause this. We don't have access to the apache/vhosts/ssl config because this site is on a shared godaddy server which has proprietary tools you have to use to manage that. The certificate is checking out OK on all the SSL checker sites I've looked at though.
– Toby
Nov 12 at 6:52
add a comment |
1
The query string shouldn't affect this by default. However, since we have no idea what your vhost settings/htaccess looks like or if there is anything in your code that does something specific if those parameters are present, we can't even begin to guess.
– Magnus Eriksson
Nov 12 at 6:47
@MagnusEriksson Thanks for your reply. I attached my htaccess file, I don't see anything obvious that would cause this. We don't have access to the apache/vhosts/ssl config because this site is on a shared godaddy server which has proprietary tools you have to use to manage that. The certificate is checking out OK on all the SSL checker sites I've looked at though.
– Toby
Nov 12 at 6:52
1
1
The query string shouldn't affect this by default. However, since we have no idea what your vhost settings/htaccess looks like or if there is anything in your code that does something specific if those parameters are present, we can't even begin to guess.
– Magnus Eriksson
Nov 12 at 6:47
The query string shouldn't affect this by default. However, since we have no idea what your vhost settings/htaccess looks like or if there is anything in your code that does something specific if those parameters are present, we can't even begin to guess.
– Magnus Eriksson
Nov 12 at 6:47
@MagnusEriksson Thanks for your reply. I attached my htaccess file, I don't see anything obvious that would cause this. We don't have access to the apache/vhosts/ssl config because this site is on a shared godaddy server which has proprietary tools you have to use to manage that. The certificate is checking out OK on all the SSL checker sites I've looked at though.
– Toby
Nov 12 at 6:52
@MagnusEriksson Thanks for your reply. I attached my htaccess file, I don't see anything obvious that would cause this. We don't have access to the apache/vhosts/ssl config because this site is on a shared godaddy server which has proprietary tools you have to use to manage that. The certificate is checking out OK on all the SSL checker sites I've looked at though.
– Toby
Nov 12 at 6:52
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53257050%2fsecure-connection-failed-ssl-error-on-php-script-depending-on-the-get-paramete%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53257050%2fsecure-connection-failed-ssl-error-on-php-script-depending-on-the-get-paramete%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
The query string shouldn't affect this by default. However, since we have no idea what your vhost settings/htaccess looks like or if there is anything in your code that does something specific if those parameters are present, we can't even begin to guess.
– Magnus Eriksson
Nov 12 at 6:47
@MagnusEriksson Thanks for your reply. I attached my htaccess file, I don't see anything obvious that would cause this. We don't have access to the apache/vhosts/ssl config because this site is on a shared godaddy server which has proprietary tools you have to use to manage that. The certificate is checking out OK on all the SSL checker sites I've looked at though.
– Toby
Nov 12 at 6:52