Adding Sites to NoJS Too Restrictive
Bug #1317462 reported by
c2t
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Midori Web Browser |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
NoJS only recognizes and allows manual add of some, but not all, sites. It seems to require name.TLD, but not all TLDs are recognized.
From what I have seen, sites NoJS does recognize, nor allow manual add of:
1. IPs
2. Newer domains that have come out, like .link and .рф (.xn--p1ai)
3. TLDs that are sites, like http://
4. Somewhat with 3, names without a TLD, like localhost
5. Custom domains that may resolve locally, like .test123
6. Anything via file:///
Using Midori 0.5.8
| Changed in midori: | |
| status: | New → Confirmed |
Revision history for this message
| gue5t gue5t (gue5t) wrote | #1 |
To post a comment you must log in.
It seems like it does accept IPv4 but not IPv6 IPs, which we should fix. Can you double-check this?
It also seems to accept .link domains and "foo.рф".
uz nor localhost are not accepted and should be fixed.
I'm not sure what the right behavior is for ".test123". It is true that it may resolve locally, but it's an invalid hostname and supporting those means we can't make assumptions which would otherwise be necessary for sanity (e.g. non-ascii hostnames should be punycode-encoded). If .test123 resolves locally, "é" (0xc3 0xa9) might as well, but there's no way to distinguish that user input from the more reasonable intent of "xn--9ca".
I don't believe midori has any way to access file:// URIs at hostnames other than localhost ("file: