[wp-trac] [WordPress Trac] #11613: HTTP API may make a request on an unsupporting transport
WordPress Trac
wp-trac at lists.automattic.com
Tue Jun 8 07:55:49 UTC 2010
#11613: HTTP API may make a request on an unsupporting transport
--------------------------+-------------------------------------------------
Reporter: dd32 | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: 3.1
Component: HTTP | Version: 2.9
Severity: normal | Keywords: has-patch
--------------------------+-------------------------------------------------
Comment(by dd32):
> then why won't you just do the check in the transport and then change
the HTTPS scheme to a HTTP one?
Changing from HTTPS to HTTP is a no-no, If someone asks for a HTTPS
connection, You give them a HTTPS connection.
The problem here is, that not all the transports can support a HTTPS
connection, If you have multiple connections being made on a pageload, the
first request determines which transport is used for that connection
So if the first request is a HTTP request, It may be made over
Class_NoSSL, Then a HTTPS request comes along (of the same GET/POST type),
it'll be passed to Class_NoSSL as ::test() passed last time.
This is due to #8622, Which should probably be fixed instead of this, or
along side.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/11613#comment:10>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list