| ??? 04/09/08 23:37 Read: times |
#153104 - I guess Responding to: ???'s previous message |
Craig Steiner said:
if I were coding such a beast on the 8052 I'd almost definitely use a single function that POSTs both "requests" and "submits." Andy Neil said:
But, from the system viewpoint, it might depend on any constraints in the Server that might or might not restrict what can & can't be used in certain cases... Of course you always have to code within any constraints you are given. If the server can't do something then obviously you can't write a client that does that "thing." Having said that I don't think there has been an HTTP server that hasn't supported POST since HTTP 1.0 which was defined in 1996. So unless your HTTP server is older than 1996 or your HTTP server was written in-house and only supports GET because that's all it needed to do, I can't imagine that an embedded client couldn't count on POST being available on the server. I believe the OP made mentions to ASP.NET which suggests to me that he's probably in the unfortunate position of using a Microsoft HTTP server. Since POST was an established part of the Internet before Microsoft even knew the Internet existed, I think it's safe to say that his target server supports POST. Though it is Microsoft so your mileage may vary. :) Regards, Craig Steiner PS--Hey, I just thought of a good way to make IIS more secure: Disable all GET and POST requests! :) |
