Forum > Networking and Web Programming

TFPHTTPClient debugging

<< < (6/6)

MvC:
About "parameters":

As the maintainer of fphttpclient, I can only agree with warfly.

The HTTP protocol expects a URL.  How this URL is constructed is not its business.

But I agree that a class (or advanced record) for easy URL constructing would be useful, but it simply must not be part of the HTTPClient class.
I have made a note to add this to the URIParser or HTTPProtocol unit.

About exceptions:

I think it is indeed possible to improve EHTTTPClient to contain the error document, and I will add this.
It has already fields for status code and text, I will check whether they are already filled.

SymbolicFrank:
@Warfley: I agree. This is for testing, and I certainly am going to URLEncode them and add a lot of other code to make it more bullet-proof, before it is production ready.

I just wasn't sure if TFPHHTPClient was the way to go.

SymbolicFrank:

--- Quote from: MvC on May 24, 2022, 11:29:52 am ---About "parameters":

As the maintainer of fphttpclient, I can only agree with warfly.

The HTTP protocol expects a URL.  How this URL is constructed is not its business.

But I agree that a class (or advanced record) for easy URL constructing would be useful, but it simply must not be part of the HTTPClient class.
I have made a note to add this to the URIParser or HTTPProtocol unit.

About exceptions:

I think it is indeed possible to improve EHTTTPClient to contain the error document, and I will add this.
It has already fields for status code and text, I will check whether they are already filled.

--- End quote ---

Thanks!

Navigation

[0] Message Index

[*] Previous page

Go to full version