Multiplexing over https: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
imported>Hendrik Brummermann Created page with '{{Navigation for Marauroa Top}} {{Navigation for Marauroa Developers}} {{Future Concept}} In order to encrypt the complete client server communication and to make the marauroa…' |
imported>Hendrik Brummermann mNo edit summary |
||
| (17 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Navigation for Marauroa Top}} |
{{Navigation for Marauroa Top|Internals}} |
||
{{Navigation for Marauroa Developers}} |
{{Navigation for Marauroa Developers}} |
||
| Line 12: | Line 12: | ||
A possible solution would be to request a sessionid with an normal https-GET-request from a php page. This php-program will store the client ip-address and the sessionid in the database. Then the client does the CONNECT-dance and sends that sessionid. If there is no sessionid, the login is rejected. If there is a sessionid, marauroa will use that to lookup the real ip-address and log it in loginEvent |
A possible solution would be to request a sessionid with an normal https-GET-request from a php page. This php-program will store the client ip-address and the sessionid in the database. Then the client does the CONNECT-dance and sends that sessionid. If there is no sessionid, the login is rejected. If there is a sessionid, marauroa will use that to lookup the real ip-address and log it in loginEvent |
||
[[Image:Https_multiplexing.png]] |
|||
[[Category:Marauroa]] |
[[Category:Marauroa]] |
||
{{#breadcrumbs: [[Marauroa]] | [[Navigation for Marauroa Developers|Internals]] | [[Marauroa Roadmap|Roadmap]] | [[Multiplexing over https]] }} |
|||