Set default userAgent if nothing else is set (redo CMS http package)

[cyrez]

Set default userAgent if nothing else is set, as it is in Joomla CMS http package.

The change introduces in joomla/joomla-cms#45751 to replace CMS Http package by the framework package with the PSR-7 interface has some difference.

The missing part to set userAgent as default if nothing else set will return a 403 error when trying to update an extension, if the update xml file is hosted on a server using a firewall.

This missing part (difference with CMS http package) in Joomla 6.0+ blocked updates for one of my update server xml hosted on OVH where their firewall was enabled. Disabling the hosting server firewall was the only way to make the update process works.

The userAgent check was introduced in this PR: joomla/joomla-cms#16538
That fixes the issue of a missing userAgent for extensions updates.

[cyrez]

A PR was opened in the CMS with much more files changed, but that may fix the issue as well: joomla/joomla-cms#46553

Just don't know the better approach: fix it in the Http framework package or in the Joomla CMS updater?

[cyrez]

Set default userAgent if nothing else is set, as it is in Joomla CMS http package.

The change introduces in joomla/joomla-cms#45751 to replace CMS Http package by the framework package with the PSR-7 interface has some difference.

The missing part to set userAgent as default if nothing else set will return a 403 error when trying to update an extension, if the update xml file is hosted on a server using a firewall.

This missing part (difference with CMS http package) in Joomla 6.0+ blocked updates for one of my update server xml hosted on OVH where their firewall was enabled. Disabling the hosting server firewall was the only way to make the update process works.

The userAgent check was introduced in this PR: joomla/joomla-cms#16538
That fixes the issue of a missing userAgent for extensions updates.

[cyrez]

A PR was opened in the CMS with much more files changed, but that may fix the issue as well: joomla/joomla-cms#46553

Just don't know the better approach: fix it in the Http framework package or in the Joomla CMS updater?

[cyrez]

Set default userAgent if nothing else is set, as it is in Joomla CMS http package.

The change introduces in joomla/joomla-cms#45751 to replace CMS Http package by the framework package with the PSR-7 interface has some difference.

The missing part to set userAgent as default if nothing else set will return a 403 error when trying to update an extension, if the update xml file is hosted on a server using a firewall.

This missing part (difference with CMS http package) in Joomla 6.0+ blocked updates for one of my update server xml hosted on OVH where their firewall was enabled. Disabling the hosting server firewall was the only way to make the update process works.

The userAgent check was introduced in this PR: joomla/joomla-cms#16538
That fixes the issue of a missing userAgent for extensions updates.

[cyrez]

A PR was opened in the CMS with much more files changed, but that may fix the issue as well: joomla/joomla-cms#46553

Just don't know the better approach: fix it in the Http framework package or in the Joomla CMS updater?

[cyrez]

Set default userAgent if nothing else is set, as it is in Joomla CMS http package.

The change introduces in joomla/joomla-cms#45751 to replace CMS Http package by the framework package with the PSR-7 interface has some difference.

The missing part to set userAgent as default if nothing else set will return a 403 error when trying to update an extension, if the update xml file is hosted on a server using a firewall.

This missing part (difference with CMS http package) in Joomla 6.0+ blocked updates for one of my update server xml hosted on OVH where their firewall was enabled. Disabling the hosting server firewall was the only way to make the update process works.

The userAgent check was introduced in this PR: joomla/joomla-cms#16538
That fixes the issue of a missing userAgent for extensions updates.

[cyrez]

A PR was opened in the CMS with much more files changed, but that may fix the issue as well: joomla/joomla-cms#46553

Just don't know the better approach: fix it in the Http framework package or in the Joomla CMS updater?

[cyrez]

Set default userAgent if nothing else is set, as it is in Joomla CMS http package.

The change introduces in joomla/joomla-cms#45751 to replace CMS Http package by the framework package with the PSR-7 interface has some difference.

The missing part to set userAgent as default if nothing else set will return a 403 error when trying to update an extension, if the update xml file is hosted on a server using a firewall.

This missing part (difference with CMS http package) in Joomla 6.0+ blocked updates for one of my update server xml hosted on OVH where their firewall was enabled. Disabling the hosting server firewall was the only way to make the update process works.

The userAgent check was introduced in this PR: joomla/joomla-cms#16538
That fixes the issue of a missing userAgent for extensions updates.

[cyrez]

A PR was opened in the CMS with much more files changed, but that may fix the issue as well: joomla/joomla-cms#46553

Just don't know the better approach: fix it in the Http framework package or in the Joomla CMS updater?

[cyrez]

Set default userAgent if nothing else is set, as it is in Joomla CMS http package.

The change introduces in joomla/joomla-cms#45751 to replace CMS Http package by the framework package with the PSR-7 interface has some difference.

The missing part to set userAgent as default if nothing else set will return a 403 error when trying to update an extension, if the update xml file is hosted on a server using a firewall.

This missing part (difference with CMS http package) in Joomla 6.0+ blocked updates for one of my update server xml hosted on OVH where their firewall was enabled. Disabling the hosting server firewall was the only way to make the update process works.

The userAgent check was introduced in this PR: joomla/joomla-cms#16538
That fixes the issue of a missing userAgent for extensions updates.

[cyrez]

A PR was opened in the CMS with much more files changed, but that may fix the issue as well: joomla/joomla-cms#46553

Just don't know the better approach: fix it in the Http framework package or in the Joomla CMS updater?

[cyrez]

Set default userAgent if nothing else is set, as it is in Joomla CMS http package.

The change introduces in joomla/joomla-cms#45751 to replace CMS Http package by the framework package with the PSR-7 interface has some difference.

The missing part to set userAgent as default if nothing else set will return a 403 error when trying to update an extension, if the update xml file is hosted on a server using a firewall.

This missing part (difference with CMS http package) in Joomla 6.0+ blocked updates for one of my update server xml hosted on OVH where their firewall was enabled. Disabling the hosting server firewall was the only way to make the update process works.

The userAgent check was introduced in this PR: joomla/joomla-cms#16538
That fixes the issue of a missing userAgent for extensions updates.

[cyrez]

A PR was opened in the CMS with much more files changed, but that may fix the issue as well: joomla/joomla-cms#46553

Just don't know the better approach: fix it in the Http framework package or in the Joomla CMS updater?

[cyrez]

Set default userAgent if nothing else is set, as it is in Joomla CMS http package.

The change introduces in joomla/joomla-cms#45751 to replace CMS Http package by the framework package with the PSR-7 interface has some difference.

The missing part to set userAgent as default if nothing else set will return a 403 error when trying to update an extension, if the update xml file is hosted on a server using a firewall.

This missing part (difference with CMS http package) in Joomla 6.0+ blocked updates for one of my update server xml hosted on OVH where their firewall was enabled. Disabling the hosting server firewall was the only way to make the update process works.

The userAgent check was introduced in this PR: joomla/joomla-cms#16538
That fixes the issue of a missing userAgent for extensions updates.

[cyrez]

A PR was opened in the CMS with much more files changed, but that may fix the issue as well: joomla/joomla-cms#46553

Just don't know the better approach: fix it in the Http framework package or in the Joomla CMS updater?