:) ;D :D Correct.
could you give me a little exemple.Something like this:
Read the standard; it's all there. As for code, it shouldn't be too difficult: connect to the server, send the request, get the response and close the connection. I'm sure you can find examples in higher libs: dive into the source of, say, fcl-web and similar and see the examples for fcl-net and alike.
Although why you want to do it with socket programming instead of using a higher level lib is a complete mistery to me :P
[...] but the syntax of GET may be so complicated to write (each browser or client sends with different syntax)
So I decided to use TidTCPClient from Indy palette, but the syntax of GET may be so complicated to write (each browser or client sends with different syntax)I don't use Indy... but I can't imagine each browser or client sends the GET differently.
@rvkYes. According to the standard.
Are you sure about the linebreak as #13#10 ? I find that rather disturbing... Protocols tend not to listen to one particular company.... That part is wrong or incomplete.
An HTTP request contains a series of lines that each end with a carriage return and a line feed, represented as either <CR><LF> or \r\n . The rest of the request contains HTTP headers, including a required Host header and, if applicable, a message body. The request ends with a bank line (an extra <CR><LF> or \r\n).
@rvkNO. Don't use sLinebreak !!! It is defined as #10 on Linux while the HTTP standard dictates you need to use #13#10 in ALL uses !! (See my quote in my previous post)
Are you sure about the linebreak as #13#10 ? I find that rather disturbing... Protocols tend not to listen to one particular company.... That part is wrong or incomplete:sLinebreak solves this cross-platform.
Do you know open source written in Delphi or FPC/lazarus flooders (http, ... ) ??Nothing.
Most my internet search I found in python and C#.
What's wrong with pascal ??