Of course there's also the issue of how much good passing credentials this way does you.
#Octoparse pass parameters free
But with the availability of free ssl certificates, and the push for "ssl everywhere", that no longer seems like much of a problem these days. I think the whole issue about removing support or deprecating the feature was based on the security implications of specifying the credentials using http protocol.
But since the https connection is encrypted, the header is encrypted and the credentials are not exposed outside the browser. Where the credentials are simply the (url-decoded) string "username:password" as written in the url, but base64-encoded. The browser extracts the credentials, and passes them to the server in an Authorization header: Authorization: Basic credentials
#Octoparse pass parameters password
Instead, just use: that you must urlencode special characters in the user or password fields (I frequently use in my passwords, so those must be written as '%40'). But unless your browser has in fact dropped the feature, then as noted in answer above, you can specify a url with basic authentication as you really should not use http protocol, since that will send the credentials in clear text. There seems to be some controversy about whether or not browsers have dropped the feature, and/or whether the feature is deprecated.
0 kommentar(er)
