6543/CommunityID
1
0
Fork 0
Code Issues 3 Pull Requests Releases Wiki Activity

import v2.0.0.0_RC3 | 2012-07-01

Browse Source 
https://github.com/lucanos/CommunityID -> http://www.itadmins.net/archives/357
This commit is contained in:
6543
2019-07-17 22:31:04 +02:00
parent 38c146901c
commit 2f397f01f7
2677 changed files with 296182 additions and 45159 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
libs/Zend/Wildfire/Channel/HttpHeaders.php
View File

@ -17,7 +17,7 @@
* @subpackage Channel
* @copyright Copyright (c) 2005-2009 Zend Technologies USA Inc. (http://www.zend.com)
* @license http://framework.zend.com/license/new-bsd New BSD License
* @version $Id: HttpHeaders.php 16971 2009-07-22 18:05:45Z mikaelkael $
* @version $Id: HttpHeaders.php 18951 2009-11-12 16:26:19Z alexander $
*/
/** Zend_Wildfire_Channel_Interface */
@ -235,10 +235,10 @@ class Zend_Wildfire_Channel_HttpHeaders extends Zend_Controller_Plugin_Abstract
*
* The channel is ready as long as the request and response objects are initialized,
* can send headers and the FirePHP header exists in the User-Agent.
*
*
* If the header does not exist in the User-Agent, no appropriate client
* is making this request and the messages should not be sent.
*
*
* A timing issue arises when messages are logged before the request/response
* objects are initialized. In this case we do not yet know if the client
* will be able to accept the messages. If we consequently indicate that
@ -246,18 +246,18 @@ class Zend_Wildfire_Channel_HttpHeaders extends Zend_Controller_Plugin_Abstract
* most cases not the intended behaviour. The intent is to send them at the
* end of the request when the request/response objects will be available
* for sure.
*
*
* If the request/response objects are not yet initialized we assume if messages are
* logged, the client will be able to receive them. As soon as the request/response
* objects are availoable and a message is logged this assumption is challenged.
* If the client cannot accept the messages any further messages are dropped
* and messages sent prior are kept but discarded when the channel is finally
* flushed at the end of the request.
*
*
* When the channel is flushed the $forceCheckRequest option is used to force
* a check of the request/response objects. This is the last verification to ensure
* messages are only sent when the client can accept them.
*
*
* @param boolean $forceCheckRequest OPTIONAL Set to TRUE if the request must be checked
* @return boolean Returns TRUE if channel is ready.
*/
@ -270,7 +270,7 @@ class Zend_Wildfire_Channel_HttpHeaders extends Zend_Controller_Plugin_Abstract
return true;
}
return ($this->getResponse()->canSendHeaders()
return ($this->getResponse()->canSendHeaders()
&& preg_match_all(
'/\s?FirePHP\/([\.|\d]*)\s?/si',
$this->getRequest()->getHeader('User-Agent'),