Set default userAgent if nothing else is set (redo CMS http package) #71
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…http package. 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
This was referenced Jan 30, 2026
Author
|
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? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.