#7458 closed defect (bug) (fixed)
curl_setopt() throws errors in safe mode
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | 2.7 |
| Component: | General | Version: | 2.7 |
| Severity: | normal | Keywords: | curl safe_mode http has-patch tested commit |
| Cc: |
Description
I'm getting the following error on each page.
Warning: curl_setopt() [function.curl-setopt]: CURLOPT_FOLLOWLOCATION cannot be activated when in safe_mode or an open_basedir is set in /**/wordpress/wp-includes/http.php on line 843
My best guess is there should be a check before running the curl-setopt function to check if safe mode is set or not.
Attachments (2)
Change History (12)
comment:3
jacobsantos — 5 years ago
I need to turn on safe mode every once and a while while I run code probably.
have you checked whether have it after the Max_redirs prevents the error?
One question, what does open_basedir have to do with whether FOLLOWLOCATION can be used? just because open_basedir is set doesn't mean safe_mode is also.
- Resolution set to fixed
- Status changed from new to closed
comment:10
santosj — 5 years ago
Oh right. The warning. That sucks.
Note: See
TracTickets for help on using
tickets.

Of course theres no mention of this on the Curl page from what i can see..
Thats not the first curl_setopt() call either, My only guess is its supposed to prevent the script from entering a endless loop? (because without CURLOPT_MAXREDIRS set, it'll follow as many as it wants -- which is done on the next line)
Perhaps, It'd be best to just not use the curl class at all in safe mode? (Its the 2nd preference for GET requests at present, not used for post?)