Skip to content
This repository has been archived by the owner on Apr 3, 2023. It is now read-only.

Feed Validation #194

Open
simonkramer opened this issue Apr 20, 2017 · 6 comments
Open

Feed Validation #194

simonkramer opened this issue Apr 20, 2017 · 6 comments

Comments

@simonkramer
Copy link

Hello,
Validation of webpages that don't provide a feed should not result in feed validation errors such as "This document has not passed the test: Feed Validator". Please correct this bug. Example: https://www.simon-kramer.ch
Best,
Simon
@ghost
Copy link

ghost commented Aug 17, 2018 •
edited by ghost
Loading

Hello,
it's not a bug... it's case-sensitive problem - the .html files must start with <!DOCTYPE html> not <!doctype ... >or something. Because it's not a tag - it's keyword and must be written upper case. (as far as I know)
But, Simon has right - the comment/explanation is not good! Simple .html caused "this feed does no validate" and "Feeds should not be served with the "text/html" media type"...
It Should be as warning like "check the declaration" or straight "change it - it's case-sensitive".

Please, correct this. I've spend many hours looking for "where is the problem"...

@simonkramer
Copy link
Author

Dear validator-lover,

Thank you for your response.

However please note that https://www.simon-kramer.ch does start with (as taught by https://www.w3schools.com/html/default.asp), but still produces an inappropriate error message.

I suspect that now the problem is that your server cannot handle http-to-https-redirects.
What do you think?

Best,

Simon

@ghost
Copy link

ghost commented Aug 22, 2018

Hi Simon!
I'm got lost - you mean your server not mine? Anyway I checked your site - it validates excellent!
I don't remember how exactly was 4 days ago, but if I wrote about lower case, I assume I looked at the source and found it there. (now is upper case and validates)
Don't ask me about server weakness :) it's not my level. I just have fun with html, css and php. Hosting cares about the rest. And unicorn of course! But, as I read/heard https makes problems :)

I repeat stubbornly - the problem exist - empty .html file should not trigger such an error message. By the way - link [help] (more information about this error) - does not work...
bye,
I still love validator

@simonkramer
Copy link
Author

Hi validator-lover,

I mean YOUR server, and my site only passes the HTML- and the CSS-test but still gives "Feed Validator"-error although my site does NOT provide an RSS-feed:

https://validator.w3.org/unicorn/check?ucn_uri=simon-kramer.ch&ucn_task=conformance

So, your RSS-feed checker does not seem to be able to cope with redirections as opposed to your HTML- and CSS-checkers, which are able to do so.

Note that when I explicitly indicate HTTPS such as with

https://validator.w3.org/unicorn/check?ucn_uri=https://simon-kramer.ch&ucn_task=conformance

there is no RSS-feed error.

So it does seem to be a configuration problem of your RSS-feed checker.

Best,

Simon

@ghost
Copy link

ghost commented Aug 22, 2018

@simonkramer writes:

Hi validator-lover,
I mean YOUR server (...) your RSS-feed checker (...) your HTML- and CSS-checkers (...) problem of your RSS-feed checker.

I'm not the 'github', 'w3c' or 'Unicorn' neither the owner of them. Got it?
I'm a (helping) user.

Apparently, your validation problems disappeared right after my first post. Spontaneously? Magically?
Now your declaration has appropriate case and validates as well!
for http:
https://validator.w3.org/unicorn/check?ucn_uri=www.simon-kramer.ch%2F&ucn_task=conformance#
for https:
https://validator.w3.org/unicorn/check?ucn_uri=https%3A%2F%2Fwww.simon-kramer.ch%2F&ucn_task=conformance#

Even if it was a magic, you should check it out instead of copy-paste old invalid results link...
Grow up

@simonkramer
Copy link
Author

Dear validator-lover,

If you are not responsible, then who is, please?

I merely meant to demonstrate that HTML- and CSS-checking behaves correctly with respect to simon-kramer.ch whereas RSS-feed checking does not.

RSS-feed checking breaks depending on the domain name prefix.

So this misbehaviour requires fixing, IMHO.

Best,

Simon

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@simonkramer