-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#32468] Fix to JHttpTransportSocket #3616
Conversation
Can you cut down the comment to one line? We don't need a full paragraph there. 😃 |
done |
Thanks for this fix, it fix for my extension. In some configuration i have only sockets extension enabled and not curl, in this case when i want update my extensions i have an error 902 displayed : http://screencast.com/t/JsoVuqqNcsi7 |
I wonder if we should not create new Joomla Issue tracker item and Add tests there |
I can put a comment into this one ^ |
@xillibit Since the JoomlaCode is not used anymore, I guess we have to lob on google groups |
I know that now we must use Jissue, do-you will open a discussion on google groups ? |
Why a discussion on Google Groups? You can discuss this tracker, right here. |
Waiting a few months is fairly standard. To improve the speed at which the issue can be progressed, it would help to have test instructions. "Every Pending issue should have instructions that tell the tester how to reproduce the problem and make sure the patch fixes the problem." http://docs.joomla.org/Bug_Tracking_Process From a code review perspective, I'm asking myself the following questions, which for me to mark a successful test would need to be satisfied. (NB: Others with more experience might waive them as unnecessary questions).
Based on a cursory code review, I'm included to give it a pass as it looks unlikely to cause any regression. |
@test Tested successfully. As this has already been committed into the framework, I don't think it needs another test. Moving to RTC. |
Is this still needed after we merged #4105? I think it achieves the same thing. |
The redirect part is, yes. |
Ah true. Then the PR should be rebased to current staging and the sort removed (which probably resolves the conflicts). |
Changing back to pending until the conflict is resolved. Using "sort" aligns with jooomla-framework. Using the "curl" preference doesn't. A decision will need to be made. |
As the stream transport doesn't currently support http redirects, I think the preferred order should be curl -> socket -> stream. i.e. Use "sort", which also benefits as it matches the joomla-framework. |
Personally I wouldn't rely on But for now I'm fine either way. Just remove the conflicts 😄 |
Fix downloads from HTTPS on servers without a global cacert.pem
Fix to Brian request : joomla#4414 <pre> Create a module with an end publishing date in the PAST. In the module list there is no visible change to its publishing status. It is still green. If you check an expired article you will see that the icon in the article list is orange not green to indicate it has expired. </pre>
Signed-off-by: Seth Warburton <seth@internet-inspired.com>
Move button before searchbox Add tooltip Fix remembering state. Simplify language string. Layout fixes. Updated icons, made them state aware. Updated language strings, made them state aware. Updated icons, alpha ordered language file, added grey background to the sidebar. Make the code abstract Added check if localStorage is available. Added code change to compressed core.js. Added toggle button to all views. Generated CSS files based on less generator. Fixed toggle buttons on user views. Update template-rtl.less. Fixed toggle button being activated on enter in filter field. Moved button to the sidebar file. Added transition changes. Cleanup banners Cleanup banners Further cleanup Further cleanup Simplify hiding the sidebar Keep the button visible Add missing empty line Updated the sidepanel. Many thanks to @RemcoJanssen Fixed Plugin view using the wrong div ID Updated CSS for RTL languages Change the icons used for closing and opening. Updated CSS for RTL.
This is probably a close tag from the default.php list view where the id is enclosed in a span element with a title set to the lft and rgt of the item. The starting tag was removed but the closing tag was still there. Removing the close tag results in a cleaner and valid html code.
@roland-d |
@piotr-cz I think your rebase went wrong. It looks like you applied all commits from staging into your branch after your own commits. Rebasing is preferred as it maintains a clean PR. However merge-commits are simpler as you just can merge the upstream staging. |
@Bakual you are right, can I undo it now or create new PR? |
You have two options:
Both ways work fine 😄 |
How to fix it? :) |
@Bakual I had moved this to RTC on 18 Sep, and now it needs re-basing? Any idea what the blocker was stoping it from being committed? |
@piotr-cz You can try to checkout an earlier version of your branch and work from there again. Or you just create a new branch based off staging and apply your changes to this clean branch. You can do that by cherrypicking the commits or by manually do the same changes again (depending how much it was you changed).
@pjwiseman Apparently the PR was in conflict with another change made recently. |
I've created a new PR#4474 rebased to master. @piotr-cz I did the following... Feel free to update your PR (which will be cleaner than using mine.) |
thanks, @pjwiseman |
joomla#3616. Fixes joomla#4474 Keep alphabetical order of detected transports across all environments Shortened description Keep alphabetical order of detected transports across all environments Added follow_location functionality to JHttpTransportSocket Shortened description
Fixes 2 issues ocuring during Extension updates:
JHttpFactory::getHttpTransports
method may return transports in random order (strange, I know), so the diver autoselection may pickJHttpTransportSocket
instead ofCurl
.follow_location
toJHttpTransportSocket
so it may handle 301-type responses.Wikipedia says: A user agent should not automatically redirect a request more than five times, since such redirections usually indicate an infinite loop.
However JHttpTransportCurl doesn't set CURLOPT_MAXREDIRS, JHttpTransportStream uses max_redirects default 20 so let's rely on severs' sanity :D
Related Issue tracker:
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=32468