How does SSH used for dynamic port forwarding know where a request wants to go?
Dynamic port forwarding using SSH uses SOCKS protocol. How does SSH know where a request wants to go? For example if the request is a HTTP request, SSH doesn't understand HTTP, so where does it find out where the HTTP request wants to go? Thanks.
ssh proxy port-forwarding socks
add a comment |
Dynamic port forwarding using SSH uses SOCKS protocol. How does SSH know where a request wants to go? For example if the request is a HTTP request, SSH doesn't understand HTTP, so where does it find out where the HTTP request wants to go? Thanks.
ssh proxy port-forwarding socks
add a comment |
Dynamic port forwarding using SSH uses SOCKS protocol. How does SSH know where a request wants to go? For example if the request is a HTTP request, SSH doesn't understand HTTP, so where does it find out where the HTTP request wants to go? Thanks.
ssh proxy port-forwarding socks
Dynamic port forwarding using SSH uses SOCKS protocol. How does SSH know where a request wants to go? For example if the request is a HTTP request, SSH doesn't understand HTTP, so where does it find out where the HTTP request wants to go? Thanks.
ssh proxy port-forwarding socks
ssh proxy port-forwarding socks
asked 20 mins ago
TimTim
26.6k77255465
26.6k77255465
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It doesn't. It creates a SOCKS proxy and the client talks the SOCKS protocol to say what it needs to do. There are no "http" requests at this layer.
The web browser speaks "SOCKS" language to say 'connect me to XYZ' and once the connection is made then it speaks HTTP (or HTTPS) to the remote server.
Similarly, a SOCKS aware SMTP client could talk SOCKS and say 'connect me to ABC' and then speaks SMTP.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f498941%2fhow-does-ssh-used-for-dynamic-port-forwarding-know-where-a-request-wants-to-go%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 doesn't. It creates a SOCKS proxy and the client talks the SOCKS protocol to say what it needs to do. There are no "http" requests at this layer.
The web browser speaks "SOCKS" language to say 'connect me to XYZ' and once the connection is made then it speaks HTTP (or HTTPS) to the remote server.
Similarly, a SOCKS aware SMTP client could talk SOCKS and say 'connect me to ABC' and then speaks SMTP.
add a comment |
It doesn't. It creates a SOCKS proxy and the client talks the SOCKS protocol to say what it needs to do. There are no "http" requests at this layer.
The web browser speaks "SOCKS" language to say 'connect me to XYZ' and once the connection is made then it speaks HTTP (or HTTPS) to the remote server.
Similarly, a SOCKS aware SMTP client could talk SOCKS and say 'connect me to ABC' and then speaks SMTP.
add a comment |
It doesn't. It creates a SOCKS proxy and the client talks the SOCKS protocol to say what it needs to do. There are no "http" requests at this layer.
The web browser speaks "SOCKS" language to say 'connect me to XYZ' and once the connection is made then it speaks HTTP (or HTTPS) to the remote server.
Similarly, a SOCKS aware SMTP client could talk SOCKS and say 'connect me to ABC' and then speaks SMTP.
It doesn't. It creates a SOCKS proxy and the client talks the SOCKS protocol to say what it needs to do. There are no "http" requests at this layer.
The web browser speaks "SOCKS" language to say 'connect me to XYZ' and once the connection is made then it speaks HTTP (or HTTPS) to the remote server.
Similarly, a SOCKS aware SMTP client could talk SOCKS and say 'connect me to ABC' and then speaks SMTP.
answered 10 mins ago
Stephen HarrisStephen Harris
25.7k24477
25.7k24477
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f498941%2fhow-does-ssh-used-for-dynamic-port-forwarding-know-where-a-request-wants-to-go%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