Bug #73330 [Opn->Fbk]: CURLOPT_RETURNTRANSFER showing different behaviour with "True" and "true"

From: Date: Mon, 17 Oct 2016 13:58:53 +0000
Subject: Bug #73330 [Opn->Fbk]: CURLOPT_RETURNTRANSFER showing different behaviour with "True" and "true"
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-204866@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=73330&edit=1 ID: 73330 Updated by: requinix@php.net Reported by: senorrishabhsoni at gmail dot com Summary: CURLOPT_RETURNTRANSFER showing different behaviour with "True" and "true" -Status: Open +Status: Feedback Type: Bug Package: cURL related Operating System: centos 6 PHP Version: 5.6.27 Block user comment: N Private report: N New Comment: Thank you for this bug report. To properly diagnose the problem, we need a short but complete example script to be able to reproduce this bug ourselves. A proper reproducing script starts with <?php and ends with ?>, is max. 10-20 lines long and does not require any external resources such as databases, etc. If the script requires a database to demonstrate the issue, please make sure it creates all necessary tables, stored procedures etc. Please avoid embedding huge scripts into the report. Previous Comments: ------------------------------------------------------------------------ [2016-10-17 13:29:26] senorrishabhsoni at gmail dot com Description: ------------ I didn't gone in deep for it. But i clearly notice the different behaviour of CURLOPT_RETURNTRANSFER with "True" and "true" flags. I was designing rest api for my project and what it does is to redirect all the url to a specific file.Then after processing, a response modules send the response header and then echoes result. With "True" there were no results at all. But by using "true" it was giving perfectly good results. I read that there is no difference between "true" and "True", although the standard is "true". I found that worth reporting. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=73330&edit=1

« previous php.bugs (#204866) next »