Closed (fixed)
Project:
Drupal core
Version:
8.3.x-dev
Component:
browser system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Sep 2016 at 14:36 UTC
Updated:
20 Feb 2017 at 13:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
chx commentedComment #3
dawehnerComment #4
hardikpandya commentedComment #5
hardikpandya commentedI have applied the patch but is unsure about how to test it.Can you please check it and suggest any changes needed?
Comment #6
dawehnerYou need to replace the call to
\Drupal::httpClient()with your new code. Well I guess you need to setup https on your local system in order to test it?Comment #7
hardikpandya commentedAdding patch.
Comment #8
dawehnerThank you
@chx
It would be great if you could confirm that this fixes your issue.
Comment #9
klausiUgh, ugly.
Can we have a comment why we need to do this? Like "Disable SSL peer verification so that testing under HTTPS always works."
Comment #10
dawehnerMaybe a pointer to #268148: Browser tests fail under HTTPS would be great as well.
Comment #11
Arndt commentedComment #12
Arndt commentedReplaced Code and added suggested Comment
Comment #13
klausiHm, looks like that is not a valid patch file? Can you create it with "git diff" as outlined on https://www.drupal.org/node/707484 ?
Comment #14
stefdewa commentedCreated valid patch based on current 8.2.x-dev.
Comment #15
klausiComment is over 80 characters, make sure to wrap the line at 80.
this line is getting long as well, let's do the array entries on separate lines.
Comment #16
stefdewa commentedAs requested comment is wrapped at a line length of 80 chars and the array entries are on separate lines.
Comment #17
stefdewa commentedComment #18
gambryManual test fails without this patch with a self-signed certificate and passes with. Happy to RTBC as soon as @klausi is happy with his feedbacks at #15.
IMHO for the sake of testing Drupal, it doesn't matter what protocol you use.
But if you HAVE TO run tests against a https environment (i.e.: due client requirements), it means the https is a requirement for you test and so it NEEDS to be a verified SSL cert.
Testing on https without verifying is more or less like testing through http.
Comment #19
gambrySorry, left-over. Reverting to Needs Review.
Comment #21
klausiThanks!
there is a comma missing on the 'verify' line.
Comment #22
stefdewa commentedAdded the missing comma.
Comment #23
klausiLooks good, thanks!
Comment #25
alexpottUnfortunately needs a re-roll.
The
Also,...can be merged with the comment on the previous line.Comment #26
jofitzRe-roll and merge comments.
Comment #27
gambryBack to RTBC then.
Comment #29
catchCommitted/pushed to 8.4.x and cherry-picked to 8.3.x, thanks!