You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
The ssl documentation/example configuration is wrong. The parameter 'ssl' => true,
doesn't work. Magento will not communicate with SSL enabled RabbitMQ.
It needs to be corrected to: 'ssl' => 'true'
where "true" must be a string (i.e. true must be in quotes.)
It looks like the code treats the ssl value as a string not as a boolean. The code in question is: trim($this->getValue(self::SSL)) === 'true';
The code is doing a '===' (i.e. value and type must be equal) which means the "ssl => ..." setting must be a string and it must be equal to 'true'.
The documented setting will not enable Magento to talk to an SSL enabled RabbitMQ instance.
Possible solutions:
Either update the documentation by putting "true" in quotes, or fix the code to treat it as a boolean instead of as a string.
Additional information:
Also noticed the warning / info blocks have incorrect formatting.
The text was updated successfully, but these errors were encountered:
General issue
Description:
The ssl documentation/example configuration is wrong. The parameter
'ssl' => true,
doesn't work. Magento will not communicate with SSL enabled RabbitMQ.
It needs to be corrected to:
'ssl' => 'true'
where "true" must be a string (i.e. true must be in quotes.)
It looks like the code treats the ssl value as a string not as a boolean. The code in question is:
trim($this->getValue(self::SSL)) === 'true';
The code is doing a '===' (i.e. value and type must be equal) which means the "ssl => ..." setting must be a string and it must be equal to 'true'.
The documented setting will not enable Magento to talk to an SSL enabled RabbitMQ instance.
Possible solutions:
Either update the documentation by putting "true" in quotes, or fix the code to treat it as a boolean instead of as a string.
Additional information:
Also noticed the warning / info blocks have incorrect formatting.
The text was updated successfully, but these errors were encountered: