CHR throws undefined index notices if "CURLOPT_WRITEFUNCTION" is used.

When CURLOPT_WRITEFUNCTION is used, curl doesn't return it's normal data structure, instead it returns 0 or 1, indicating whether the function past in WRITEFUNCTION completed successfully.

This causes notices to be thrown during the HTTP respond parsing.

CommentFileSizeAuthor
#2 chr-notices-27539430-1.patch780 bytesspotzero

Comments

spotzero created an issue. See original summary.

spotzero’s picture

spotzero commented
StatusFileSize
new chr-notices-27539430-1.patch780 bytes

The attached patch resolves the notices. Unfortunately, the CHR module can't know the true response code in the above situation, so '200' is assumed so that the rest of the code functions normally.