>
>Could libURL be extended to allow users of it to customise the headers of
>outgoing HTTP requests, and read the headers of incoming HTTP responses,
>without losing the benefits of having the library (ie, without requiring
>each developer to customise the library themselves).
The easiest way is to manipulate the custom properties of libURL (the headers): get
the list
of them, choose which one you want to change and set it to whatever you want.
A replacement to the old httpHeaders I sugested is to have the library use a totally
new
custom header as opposed to adding to an existing one, similar to what you propose
bellow.
>
>A crude (but effective) solution would be to declare a couple of global
>variables or properties; eg "gHTTPrequestExtraHeaders" and "gHTTPresponse".
>Each call to "get URL xxx" would consult the first global, and set the
>second. It might be up to the user to empty the gHTTPrequestExtraHeaders
>after use, or libURL could empty it after each call.
>
>No doubt more expert MC users could propose a more sophisticated syntax (eg
>is it possible to make the URL support a syntax such as "get URL xx with
>headers yy"?)
>
> Ben Rubinstein | Email: [EMAIL PROTECTED]
> Cognitive Applications Ltd | Phone: +44 (0)1273-821600
> http://www.cogapp.com | Fax : +44 (0)1273-728866
>
>
>Archives: http://www.mail-archive.com/[email protected]/
>Info: http://www.xworlds.com/metacard/mailinglist.htm
>Please send bug reports to <[EMAIL PROTECTED]>, not this list.
>
>.
Regards, Andu
______________
[EMAIL PROTECTED]
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
