On 5/18/2010 9:34 AM, Stefan Rossbach wrote:
I'm trying to get SSTP to work. The HTTPS configuration works fine, after the cert conversion war ;-), but I run into the following problem:pound: (7f4e8d5a7910) e501 bad request "SSTP_DUPLEX_POST /sra_{BA195980-CD49-458b-9E23-C84EE0ADCD75}/ HTTP/1.1" from x.x.x.x xHTTP is set to 4
4 is a good start. You'll need to patch pound so it understands the SSTP_DUPLEX_POST verb (it doesn't, as the log tells you). Maybe add a '5' value, or just extend the verbs allowed by '4'.
I've found the following information here: http://blogs.technet.com/rrasblog/archive/2007/03/07/configuring-sstp-in-a-reverse-proxy-scenario.aspx
The article assumes you can tell your SSL terminator in a conf file or something about the new verb used for SSTP. In pound's case this requires patching the source code.
"The HTTP method to look for will be SSTP_DUPLEX_POST. This is the verb that SSTP uses (which is similar to GET/PUT/POST)." I found as well a connection scheme for connect over proxy: http://msdn.microsoft.com/en-us/library/cc247411%28PROT.10%29.aspx In my opinion it should be easy to implement but how?
Just read the source and try adding support for the new verb. Pound is very readable. If you want to get fancy, you can try adding a configuration directive to allow additional verbs specified in the conf.
PS - Adding support for the verb is merely the first step. I have no idea if it'll work even if you successfully do that - there may be other issues involved that you discover later.
Regards, -- Dave Steinberg http://www.geekisp.com/ http://www.steinbergcomputing.com/ -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
