Bug #8361

#1176475350: More than one.. when Request Handler Name is cgi-fcgi

Added by Manfred Siegmund about 5 years ago. Updated about 4 years ago.

Status:Closed Start date:2010-06-20
Priority:Must have Due date:
Assigned To:Karsten Dambekalns % Done:

0%

Category:MVC
Target version:-
PHP Version: Complexity:
Has patch: Affected Flow version:

Description

I installed flow on a domaingo (Domainfactory) Power XL Webhosting.

Beside some restrictions on the hosters part (setenv in .htaccess is invalid and must be set inside the index.php as putenv) the installation was easy and fast with the flow3 online help.
Everything went ok, the welcome page showed up and said i should use ./flow3 functions to deactivate the Welcome package and
setup a MyPackage. (I am testing flow3 on zox-systems.net Domaingo Power XL Webhosting)

Using the Putty Terminal i can either type ./flow3 .... or sh flow3 ... means i can use the commandos and the flow3 script on the ssh terminal.
When running any flow3 commands i receive a Flow3 Exception #1176475350: More than one request handler with the same priority can handle the request, but only one handler may be active at a time!

After a couple cups of Coffee and the look in the sources (/Packages/Framework/FLOW3/Classes/MVC/CLI/RequestHandler.php line 87) i found following solution.

The return $this->utilityEnvironment->getSAPIName() === 'cli' is only valid for the web output, but triggers the exception above within the shell.
I changed following parts of /Packages/Framework/FLOW3/Classes/MVC/CLI/RequestHandler.php and the output of the Web, the shell works as expected on my Domaingo Power XL installation.

public function canHandleRequest() {
if($this->utilityEnvironment->getSAPIName() 'cgi-fcgi'){
return ($this->utilityEnvironment->getSAPIName() = 'cgi-fcgi');
}
#return ($this->utilityEnvironment->getSAPIName() === 'cli');
}

public function getPriority() {
if($this->utilityEnvironment->getSAPIName() == 'cgi-fcgi'){
return 0;
}else{
return 100;
}
}

Expect:
There should be a SetEnv or other configuration flag to configure the request handler name in such cases.

History

#1 Updated by Karsten Dambekalns about 5 years ago

  • Target version deleted (1.0 alpha 8)

#2 Updated by Karsten Dambekalns about 4 years ago

  • Status changed from New to Closed
  • Assigned To set to Karsten Dambekalns

Outdated and never verified.

Also available in: Atom PDF