Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Consider supporting invalid URLs only starting with `www.` without a scheme

See original GitHub issue

Feed URL: https://www.waterfox.net/feed.xml

Add-on version: 2.8

Describe the bug It creates a folder, but doesn’t fetch any items. Main item has a strange address https://www.waterfox.net/www.waterfox.net/. I use Waterfox Current. In Waterfox Classic which is based on old Firefox the build-in subscription works properly and preview displays all items properly, so it might be an add-on bug.

To Reproduce Steps to reproduce the behavior:

Go to ‘https://www.waterfox.net/’
Click on ‘feed icon’ at the bottom of the page
Add Livemark
Go to created folder

Expected behavior Live bookmark folder should be properly created.

Issue Analytics

State:
Created 3 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

nt1mcommented, Apr 20, 2020

Thanks for reporting!

This feed is invalid according to the specification, URLs should either include the scheme (“https://” or “http://”) or should use real relative URLs (so “/blog/waterfox-2020.04-release/” with nothing else). Right now, it uses the “www.waterfox.net/blog/waterfox-2020.04-release/” format, which does neither…

The fact that it works in some feed readers is because they special case this invalid URL format, this could be done, but I think this blog should really fix its feed.

I did notice Livemarks doesn’t support relative URLs for Atom feeds, but that’s a different issue that’s separate from this one.

0reactions

nt1mcommented, Apr 21, 2020

I mean there could be an option to manually choose what to add per feed. I was thinking exactly the same that there could be many possibilities how feed would be made. So if users could specify by themselves that than just only let it automatically determine.

A manual setting wouldn’t fix the issue for the feed preview page, at that point, the setting is not set by the user yet. Not to mention, a single feed contains multiple URLs, which may have different URL formats.

Automatic detection would take as much time as adding a manual setting. I don’t have much time this month unfortunately.

Top Results From Across the Web

Validate URL without scheme - Stack Overflow

I'm aware of the change with schemes (iOS9+) and I know that I can just add a prefix like "http://" if the String...

Invalid URL - Google Merchant Center Help

A URL in your data feed is badly formed or contains invalid characters. There are several common reasons why you might receive this...

HTTPS Request: Invalid scheme for Http · Issue #1009 - GitHub

I'm currently building against v0.10 and am experiencing some issues trying to send a request on macOS 10.12. Here's a minimal example.

Choosing between www and non-www URLs - HTTP | MDN

In this case, you need to configure the server receiving the HTTP requests (which is most likely the same for www and non-www...

RFC 1738 Uniform Resource Locators (URL) December 1994

No corresponding graphic US-ASCII: URLs are written only with the graphic printable ... and file schemes) contain names that can be considered hierarchical; ......