Skip to content

[4.0-dev] Add userAgent check#16538

Merged
wilsonge merged 10 commits intojoomla:4.0-devfrom
zero-24:setUserAgentIfNotSet
Jul 29, 2017
Merged

[4.0-dev] Add userAgent check#16538
wilsonge merged 10 commits intojoomla:4.0-devfrom
zero-24:setUserAgentIfNotSet

Conversation

@zero-24
Copy link
Copy Markdown
Contributor

@zero-24 zero-24 commented Jun 5, 2017

Pull Request for Issue #16172

Summary of Changes

Set default useragent on all JHttpFactory calls #16172

Testing Instructions

Do a call with JHttpFactory and confirm that the UserAgent is set.
Set a useragent & try again

Expected result

userAgent is set.

Actual result

userAgent is not set.

Documentation Changes Required

None

@wilsonge wilsonge merged commit 3a8af4e into joomla:4.0-dev Jul 29, 2017
@wilsonge
Copy link
Copy Markdown
Contributor

Thanks!

@zero-24 zero-24 deleted the setUserAgentIfNotSet branch July 29, 2017 13:50
cyrez added a commit to cyrez/http that referenced this pull request Jan 30, 2026
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants