Allow easier access to site on a http:// URL
See original GitHub issueCurrently, the URL scheme used to access the MediaWiki instance is hardcoded to https
in the raw_call
function of client.py
. This makes it impossible to use mwclient wit a wiki which is hosted under an unencrypted http:// URL.
This should be made configurable (either by adding a scheme parameter to the Site constructor or by allowing a full URL instead of just the hostname there).
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Allow or block access to websites - Google Support
As a Chrome Enterprise admin you can block and allow URLs so that users can only visit certain websites. Restricting users' internet access...
Read more >Enabling HTTPS on your servers - web.dev
Enabling HTTPS on your servers is critical to securing your webpages.
Read more >Cross-Origin Resource Sharing (CORS) - MDN Web Docs
This cross-origin sharing standard can enable cross-origin HTTP ... cross-site XMLHttpRequest and fetch ) can submit simple requests to any ...
Read more >Restricting access to specific URLs
To configure an URL access rule ; 1. Go to Web Protection > Access > URL Access and select the URL Access Rule...
Read more >Good Practices for Capability URLs - W3C
Capability URLs grant access to a resource to anyone who has the URL. There are times when this is useful, for example one-shot...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve only kept it for backwards compatibility, but I wouldn’t mind if we introduced a new parameter and deprecated the old syntax and then removed it with the next major release or something.
@danmichaelo shall we reopen #213 then (and this issue as well), provided that it also removes the special handling of the
host
parameter in the code I quoted above?