What can cause cutting of the slash in the url?
up vote
0
down vote
favorite
Let's say I have url similar to this:
https://sprerererer.blablabla.systems/confirm-reservation/5cbe0e49e611ac1f06b39342a9b35c93a69cef6f8fbe6136752af4c8fe86eb64323031382d31312d31392031313a30303a3434
(due to security reasons, it's not my real url)
If I paste it to chrome it redirects me to:
https://sprerererer.blablabla.systemsconfirm-reservation/5cbe0e49e611ac1f06b39342a9b35c93a69cef6f8fbe6136752af4c8fe86eb64323031382d31312d31392031313a30303a3434
cutting of the slash at the end of domain. I never encountered anything like it. What can cause it? Is it chrome? Is it my server's fault?
http url https
asked Nov 19 at 11:07
Tutu Kaeen
22729
|
show 2 more comments
up vote
0
down vote
favorite
Let's say I have url similar to this:
https://sprerererer.blablabla.systems/confirm-reservation/5cbe0e49e611ac1f06b39342a9b35c93a69cef6f8fbe6136752af4c8fe86eb64323031382d31312d31392031313a30303a3434
(due to security reasons, it's not my real url)
If I paste it to chrome it redirects me to:
https://sprerererer.blablabla.systemsconfirm-reservation/5cbe0e49e611ac1f06b39342a9b35c93a69cef6f8fbe6136752af4c8fe86eb64323031382d31312d31392031313a30303a3434
cutting of the slash at the end of domain. I never encountered anything like it. What can cause it? Is it chrome? Is it my server's fault?
http url https
asked Nov 19 at 11:07
Tutu Kaeen
22729
1
Most likely the cause is some redirection rule implemented on the server side. Either on the level of the http server or inside the applicatiohn logic you use.
– arkascha
Nov 19 at 11:13
And by the way: there is absolutely no reason to obfuscate your URLs. That does not offer additional security, it typically only indicates an undefined fear that the own solution is everything but robust. Think of it this way: if you publish something on the internet (which you apparently do), then what you publish is available. So it needs to have a level of quality that you trust in so that you dare to publish it. Or the effects of a lower quality is so trivial that you dare it anyway. If the only measure for quality you take is to "keep your URLs secret" then you have a very deep problem.
– arkascha
Nov 19 at 11:16
@arkascha - I strongly disagree, I am almost sure that if I asked about security problem on a production website and I have and posted my real url here, somebody would try to break it. My problem is not very vulnerable I think, but I still don't see any reason why should I post my real website url.
– Tutu Kaeen
Nov 19 at 11:20
Certainly my remark also applies to production systems. Your solution needs to be that rubost that you can grant everyone to try to break it. Everything else means that you are afraid of reality. Keeping a URL secret won't work, that is naive. Obfuscation does not offer security, it only makes things more complex and less secure in the end, since if offers a false sense of security.
– arkascha
Nov 19 at 11:23
sure, I get your point, but right now I KNOW that my system is vulnerable and by asking questions here I'm trying to make it more secure. I wouldn't ask questions here if I would be sure of quality of my product as of this moment. And I think your post applies more to finished and tested products, not work in progress.
– Tutu Kaeen
Nov 19 at 11:28
|
show 2 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Let's say I have url similar to this:
https://sprerererer.blablabla.systems/confirm-reservation/5cbe0e49e611ac1f06b39342a9b35c93a69cef6f8fbe6136752af4c8fe86eb64323031382d31312d31392031313a30303a3434
(due to security reasons, it's not my real url)
If I paste it to chrome it redirects me to:
https://sprerererer.blablabla.systemsconfirm-reservation/5cbe0e49e611ac1f06b39342a9b35c93a69cef6f8fbe6136752af4c8fe86eb64323031382d31312d31392031313a30303a3434
cutting of the slash at the end of domain. I never encountered anything like it. What can cause it? Is it chrome? Is it my server's fault?
http url https
asked Nov 19 at 11:07
Tutu Kaeen
22729
Let's say I have url similar to this:
https://sprerererer.blablabla.systems/confirm-reservation/5cbe0e49e611ac1f06b39342a9b35c93a69cef6f8fbe6136752af4c8fe86eb64323031382d31312d31392031313a30303a3434
(due to security reasons, it's not my real url)
If I paste it to chrome it redirects me to:
https://sprerererer.blablabla.systemsconfirm-reservation/5cbe0e49e611ac1f06b39342a9b35c93a69cef6f8fbe6136752af4c8fe86eb64323031382d31312d31392031313a30303a3434
cutting of the slash at the end of domain. I never encountered anything like it. What can cause it? Is it chrome? Is it my server's fault?
http url https
http url https
asked Nov 19 at 11:07
Tutu Kaeen
22729
asked Nov 19 at 11:07
Tutu Kaeen
22729
asked Nov 19 at 11:07
Tutu Kaeen
22729
asked Nov 19 at 11:07
Tutu Kaeen
22729
asked Nov 19 at 11:07
Tutu Kaeen
22729
22729
1
Most likely the cause is some redirection rule implemented on the server side. Either on the level of the http server or inside the applicatiohn logic you use.
– arkascha
Nov 19 at 11:13
And by the way: there is absolutely no reason to obfuscate your URLs. That does not offer additional security, it typically only indicates an undefined fear that the own solution is everything but robust. Think of it this way: if you publish something on the internet (which you apparently do), then what you publish is available. So it needs to have a level of quality that you trust in so that you dare to publish it. Or the effects of a lower quality is so trivial that you dare it anyway. If the only measure for quality you take is to "keep your URLs secret" then you have a very deep problem.
– arkascha
Nov 19 at 11:16
@arkascha - I strongly disagree, I am almost sure that if I asked about security problem on a production website and I have and posted my real url here, somebody would try to break it. My problem is not very vulnerable I think, but I still don't see any reason why should I post my real website url.
– Tutu Kaeen
Nov 19 at 11:20
Certainly my remark also applies to production systems. Your solution needs to be that rubost that you can grant everyone to try to break it. Everything else means that you are afraid of reality. Keeping a URL secret won't work, that is naive. Obfuscation does not offer security, it only makes things more complex and less secure in the end, since if offers a false sense of security.
– arkascha
Nov 19 at 11:23
sure, I get your point, but right now I KNOW that my system is vulnerable and by asking questions here I'm trying to make it more secure. I wouldn't ask questions here if I would be sure of quality of my product as of this moment. And I think your post applies more to finished and tested products, not work in progress.
– Tutu Kaeen
Nov 19 at 11:28
|
show 2 more comments
1
Most likely the cause is some redirection rule implemented on the server side. Either on the level of the http server or inside the applicatiohn logic you use.
– arkascha
Nov 19 at 11:13
And by the way: there is absolutely no reason to obfuscate your URLs. That does not offer additional security, it typically only indicates an undefined fear that the own solution is everything but robust. Think of it this way: if you publish something on the internet (which you apparently do), then what you publish is available. So it needs to have a level of quality that you trust in so that you dare to publish it. Or the effects of a lower quality is so trivial that you dare it anyway. If the only measure for quality you take is to "keep your URLs secret" then you have a very deep problem.
– arkascha
Nov 19 at 11:16
@arkascha - I strongly disagree, I am almost sure that if I asked about security problem on a production website and I have and posted my real url here, somebody would try to break it. My problem is not very vulnerable I think, but I still don't see any reason why should I post my real website url.
– Tutu Kaeen
Nov 19 at 11:20
Certainly my remark also applies to production systems. Your solution needs to be that rubost that you can grant everyone to try to break it. Everything else means that you are afraid of reality. Keeping a URL secret won't work, that is naive. Obfuscation does not offer security, it only makes things more complex and less secure in the end, since if offers a false sense of security.
– arkascha
Nov 19 at 11:23
sure, I get your point, but right now I KNOW that my system is vulnerable and by asking questions here I'm trying to make it more secure. I wouldn't ask questions here if I would be sure of quality of my product as of this moment. And I think your post applies more to finished and tested products, not work in progress.
– Tutu Kaeen
Nov 19 at 11:28
1
1
Most likely the cause is some redirection rule implemented on the server side. Either on the level of the http server or inside the applicatiohn logic you use.
– arkascha
Nov 19 at 11:13
Most likely the cause is some redirection rule implemented on the server side. Either on the level of the http server or inside the applicatiohn logic you use.
– arkascha
Nov 19 at 11:13
And by the way: there is absolutely no reason to obfuscate your URLs. That does not offer additional security, it typically only indicates an undefined fear that the own solution is everything but robust. Think of it this way: if you publish something on the internet (which you apparently do), then what you publish is available. So it needs to have a level of quality that you trust in so that you dare to publish it. Or the effects of a lower quality is so trivial that you dare it anyway. If the only measure for quality you take is to "keep your URLs secret" then you have a very deep problem.
– arkascha
Nov 19 at 11:16
And by the way: there is absolutely no reason to obfuscate your URLs. That does not offer additional security, it typically only indicates an undefined fear that the own solution is everything but robust. Think of it this way: if you publish something on the internet (which you apparently do), then what you publish is available. So it needs to have a level of quality that you trust in so that you dare to publish it. Or the effects of a lower quality is so trivial that you dare it anyway. If the only measure for quality you take is to "keep your URLs secret" then you have a very deep problem.
– arkascha
Nov 19 at 11:16
@arkascha - I strongly disagree, I am almost sure that if I asked about security problem on a production website and I have and posted my real url here, somebody would try to break it. My problem is not very vulnerable I think, but I still don't see any reason why should I post my real website url.
– Tutu Kaeen
Nov 19 at 11:20
@arkascha - I strongly disagree, I am almost sure that if I asked about security problem on a production website and I have and posted my real url here, somebody would try to break it. My problem is not very vulnerable I think, but I still don't see any reason why should I post my real website url.
– Tutu Kaeen
Nov 19 at 11:20
Certainly my remark also applies to production systems. Your solution needs to be that rubost that you can grant everyone to try to break it. Everything else means that you are afraid of reality. Keeping a URL secret won't work, that is naive. Obfuscation does not offer security, it only makes things more complex and less secure in the end, since if offers a false sense of security.
– arkascha
Nov 19 at 11:23
Certainly my remark also applies to production systems. Your solution needs to be that rubost that you can grant everyone to try to break it. Everything else means that you are afraid of reality. Keeping a URL secret won't work, that is naive. Obfuscation does not offer security, it only makes things more complex and less secure in the end, since if offers a false sense of security.
– arkascha
Nov 19 at 11:23
sure, I get your point, but right now I KNOW that my system is vulnerable and by asking questions here I'm trying to make it more secure. I wouldn't ask questions here if I would be sure of quality of my product as of this moment. And I think your post applies more to finished and tested products, not work in progress.
– Tutu Kaeen
Nov 19 at 11:28
sure, I get your point, but right now I KNOW that my system is vulnerable and by asking questions here I'm trying to make it more secure. I wouldn't ask questions here if I would be sure of quality of my product as of this moment. And I think your post applies more to finished and tested products, not work in progress.
– Tutu Kaeen
Nov 19 at 11:28
|
show 2 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f53373314%2fwhat-can-cause-cutting-of-the-slash-in-the-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
1
Most likely the cause is some redirection rule implemented on the server side. Either on the level of the http server or inside the applicatiohn logic you use.
– arkascha
Nov 19 at 11:13
And by the way: there is absolutely no reason to obfuscate your URLs. That does not offer additional security, it typically only indicates an undefined fear that the own solution is everything but robust. Think of it this way: if you publish something on the internet (which you apparently do), then what you publish is available. So it needs to have a level of quality that you trust in so that you dare to publish it. Or the effects of a lower quality is so trivial that you dare it anyway. If the only measure for quality you take is to "keep your URLs secret" then you have a very deep problem.
– arkascha
Nov 19 at 11:16
@arkascha - I strongly disagree, I am almost sure that if I asked about security problem on a production website and I have and posted my real url here, somebody would try to break it. My problem is not very vulnerable I think, but I still don't see any reason why should I post my real website url.
– Tutu Kaeen
Nov 19 at 11:20
Certainly my remark also applies to production systems. Your solution needs to be that rubost that you can grant everyone to try to break it. Everything else means that you are afraid of reality. Keeping a URL secret won't work, that is naive. Obfuscation does not offer security, it only makes things more complex and less secure in the end, since if offers a false sense of security.
– arkascha
Nov 19 at 11:23
sure, I get your point, but right now I KNOW that my system is vulnerable and by asking questions here I'm trying to make it more secure. I wouldn't ask questions here if I would be sure of quality of my product as of this moment. And I think your post applies more to finished and tested products, not work in progress.
– Tutu Kaeen
Nov 19 at 11:28