Special character '@' in URL
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Using the symbol @ in middle of the URL such as https://www.google.com@stackoverflow.com redirects to https://stackoverflow.com/ site (domain URL after @ character).
Why does it redirect to domain mentioned at the end of the URL? Can we stop this type of redirection?
I found that the text before @ is considered as username and the domain name followed by @ is considered as email server, so it is automatically redirected.
http url
edited Nov 17 '18 at 23:53
unor
68.3k17146251
asked Nov 16 '18 at 14:38
PrabhaPrabha
7312
add a comment |
Using the symbol @ in middle of the URL such as https://www.google.com@stackoverflow.com redirects to https://stackoverflow.com/ site (domain URL after @ character).
Why does it redirect to domain mentioned at the end of the URL? Can we stop this type of redirection?
I found that the text before @ is considered as username and the domain name followed by @ is considered as email server, so it is automatically redirected.
http url
edited Nov 17 '18 at 23:53
unor
68.3k17146251
asked Nov 16 '18 at 14:38
PrabhaPrabha
7312
add a comment |
Using the symbol @ in middle of the URL such as https://www.google.com@stackoverflow.com redirects to https://stackoverflow.com/ site (domain URL after @ character).
Why does it redirect to domain mentioned at the end of the URL? Can we stop this type of redirection?
I found that the text before @ is considered as username and the domain name followed by @ is considered as email server, so it is automatically redirected.
http url
edited Nov 17 '18 at 23:53
unor
68.3k17146251
asked Nov 16 '18 at 14:38
PrabhaPrabha
7312
Using the symbol @ in middle of the URL such as https://www.google.com@stackoverflow.com redirects to https://stackoverflow.com/ site (domain URL after @ character).
Why does it redirect to domain mentioned at the end of the URL? Can we stop this type of redirection?
I found that the text before @ is considered as username and the domain name followed by @ is considered as email server, so it is automatically redirected.
http url
http url
edited Nov 17 '18 at 23:53
unor
68.3k17146251
asked Nov 16 '18 at 14:38
PrabhaPrabha
7312
edited Nov 17 '18 at 23:53
unor
68.3k17146251
asked Nov 16 '18 at 14:38
PrabhaPrabha
7312
edited Nov 17 '18 at 23:53
unor
68.3k17146251
edited Nov 17 '18 at 23:53
unor
68.3k17146251
edited Nov 17 '18 at 23:53
unor
68.3k17146251
68.3k17146251
asked Nov 16 '18 at 14:38
PrabhaPrabha
7312
asked Nov 16 '18 at 14:38
PrabhaPrabha
7312
asked Nov 16 '18 at 14:38
PrabhaPrabha
7312
7312
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It's not a redirect, this is part of the URL standard itself, and no this can't be stopped. If you need the @ character, you'll have to URL-encode it (but this still won't work in the domain name itself, I believe)
From the URL RFC:
While the syntax for the rest of the URL may vary depending on the
particular scheme selected, URL schemes that involve the direct use
of an IP-based protocol to a specified host on the Internet use a
common syntax for the scheme-specific data:
//<user>:<password>@<host>:<port>/<url-path>
Some or all of the parts ":@", ":",
":", and "/" may be excluded.
answered Nov 16 '18 at 14:50
declensiondeclension
3,1491420
add a comment |
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',
autoActivateHeartbeat: false,
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%2f53339945%2fspecial-character-in-url%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It's not a redirect, this is part of the URL standard itself, and no this can't be stopped. If you need the @ character, you'll have to URL-encode it (but this still won't work in the domain name itself, I believe)
From the URL RFC:
While the syntax for the rest of the URL may vary depending on the
particular scheme selected, URL schemes that involve the direct use
of an IP-based protocol to a specified host on the Internet use a
common syntax for the scheme-specific data:
//<user>:<password>@<host>:<port>/<url-path>
Some or all of the parts ":@", ":",
":", and "/" may be excluded.
answered Nov 16 '18 at 14:50
declensiondeclension
3,1491420
add a comment |
It's not a redirect, this is part of the URL standard itself, and no this can't be stopped. If you need the @ character, you'll have to URL-encode it (but this still won't work in the domain name itself, I believe)
From the URL RFC:
While the syntax for the rest of the URL may vary depending on the
particular scheme selected, URL schemes that involve the direct use
of an IP-based protocol to a specified host on the Internet use a
common syntax for the scheme-specific data:
//<user>:<password>@<host>:<port>/<url-path>
Some or all of the parts ":@", ":",
":", and "/" may be excluded.
answered Nov 16 '18 at 14:50
declensiondeclension
3,1491420
add a comment |
It's not a redirect, this is part of the URL standard itself, and no this can't be stopped. If you need the @ character, you'll have to URL-encode it (but this still won't work in the domain name itself, I believe)
From the URL RFC:
While the syntax for the rest of the URL may vary depending on the
particular scheme selected, URL schemes that involve the direct use
of an IP-based protocol to a specified host on the Internet use a
common syntax for the scheme-specific data:
//<user>:<password>@<host>:<port>/<url-path>
Some or all of the parts ":@", ":",
":", and "/" may be excluded.
answered Nov 16 '18 at 14:50
declensiondeclension
3,1491420
It's not a redirect, this is part of the URL standard itself, and no this can't be stopped. If you need the @ character, you'll have to URL-encode it (but this still won't work in the domain name itself, I believe)
From the URL RFC:
While the syntax for the rest of the URL may vary depending on the
particular scheme selected, URL schemes that involve the direct use
of an IP-based protocol to a specified host on the Internet use a
common syntax for the scheme-specific data:
//<user>:<password>@<host>:<port>/<url-path>
Some or all of the parts ":@", ":",
":", and "/" may be excluded.
answered Nov 16 '18 at 14:50
declensiondeclension
3,1491420
answered Nov 16 '18 at 14:50
declensiondeclension
3,1491420
answered Nov 16 '18 at 14:50
declensiondeclension
3,1491420
answered Nov 16 '18 at 14:50
declensiondeclension
3,1491420
3,1491420
add a comment |
add a comment |
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.
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%2f53339945%2fspecial-character-in-url%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
