Timeline for Authenticating a Proxy server over HTTPS
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2022 at 8:06 | history | edited | Glorfindel | CC BY-SA 4.0 | broken link fixed, cf. https://meta.stackoverflow.com/a/406565/4751173 |
| Jul 6, 2013 at 13:55 | history | edited | makerofthings7 | CC BY-SA 3.0 | added 198 characters in body |
| Nov 29, 2012 at 13:36 | comment | added | makerofthings7 | @AviD Just as the SSH solution takes on the responsibility of identifying the proxy, this would do the same. Just point the client to a local port, and the data is secured and managed by the service bus until it reaches the destination (your proxy). | |
| Nov 29, 2012 at 8:53 | comment | added | AviD♦ | I'm not sure I understand, or maybe you missed the point of the question. Using standard HTTP, how would this help verify the identity of the proxy? | |
| Nov 29, 2012 at 5:22 | history | edited | makerofthings7 | CC BY-SA 3.0 | added 124 characters in body |
| Nov 29, 2012 at 4:46 | history | edited | makerofthings7 | CC BY-SA 3.0 | added 206 characters in body |
| Nov 29, 2012 at 4:41 | history | answered | makerofthings7 | CC BY-SA 3.0 |