Components | All | New | MacOS | Windows | Linux | iOS | ||||
Examples | Mac & Win | Server | Client | Guides | Statistic | FMM | Blog | Deprecated | Old |
CURL.CreateHeaderOutputFile
Creates output file for writing header text.
Component | Version | macOS | Windows | Linux | Server | iOS SDK |
CURL | 2.6 | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes |
MBS( "CURL.CreateHeaderOutputFile"; curl; Path ) More
Parameters
Parameter | Description | Example |
---|---|---|
curl | The CURL session handle. | $curl |
Path | Native file path. | C:\Documents\Test.Txt |
Result
Returns "OK" on success or error message.
Description
Creates output file for writing header text.Header messages are written to file if you use this functions and header text are always collected for calling CURL.GetHeaders after the transfer. This can be useful as you can have your FileMaker solution write a copy of headers in temporary file. If your client has problems, you can simply read headers from last transfer. If creation of the file fails, you get an error message back, but still your transfer will probably succeed.
Do not call this method while a transfer is running.
This function requires a native path. Use Path.FileMakerPathToNativePath to convert a FileMaker path to a native path if required. If you like to have the user choose the path, you can use FileDialog functions.
For Server be aware that server has limited permissions and may not be able to access all files on a computer.
Examples
Write copy of header texts to a file into temp folder on Mac:
MBS( "CURL.CreateHeaderOutputFile"; $curl; "/tmp/LastHeaders.txt" )
See also
- CURL.CloseHeaderFile
- CURL.CreateDebugOutputFile
- CURL.CreateOutputFile
- CURL.GetHeaders
- Path.FileMakerPathToNativePath
Example Databases
Blog Entries
This function checks for a license.
Created 18th August 2014, last changed 3th January 2023