Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RSS links get served as text/html #20

Open
xet7 opened this issue Mar 8, 2018 · 10 comments
Open

RSS links get served as text/html #20

xet7 opened this issue Mar 8, 2018 · 10 comments

Comments

@xet7
Copy link
Member

xet7 commented Mar 8, 2018

From @mrdomino on July 21, 2016 19:53

On my private site, if I visit /feed/, I get a response content-type of application/rss+xml. On the public site, that link gets rewritten as /feed/index.html and served as text/html. This seems weird. I can't tell if this is bad or not, aside from causing Chrome to try to render it.

Copied from original issue: dwrensha/wordpress-sandstorm#26

@xet7
Copy link
Member Author

xet7 commented Mar 8, 2018

From @ocdtrekkie on July 21, 2016 21:35

For what it's worth, I think most web browsers will try to provide a navigable rendered UI for XML files these days. But probably only if they can tell it's XML.

@xet7
Copy link
Member Author

xet7 commented Mar 8, 2018

From @mrdomino on July 21, 2016 21:36

There's definitely a difference in Chrome between the two content types: visiting /feed on my private site shows XML source, whereas /feed on the public site shows a badly mangled rendering of the XML as though it were HTML.

@xet7
Copy link
Member Author

xet7 commented Mar 8, 2018

From @mrdomino on July 21, 2016 21:37

(Re-reading your comment, I now think you were saying that it's okay to serve up the content as XML. I'd agree.)

@xet7
Copy link
Member Author

xet7 commented Mar 8, 2018

From @dwrensha on July 21, 2016 21:39

I think the issue here is that our wget hack for generating static content is not smart enough to properly handle XML.

@xet7
Copy link
Member Author

xet7 commented Mar 8, 2018

From @mrdomino on July 21, 2016 21:40

I'm now tempted to rewrite that in Python.

@xet7
Copy link
Member Author

xet7 commented Mar 8, 2018

From @dwrensha on July 21, 2016 21:42

It's possible that wget has learned some new tricks in the past two years and now has a nice way to deal with this kind of thing.

@xet7
Copy link
Member Author

xet7 commented Mar 8, 2018

From @paulproteus on July 21, 2016 21:46

IMHO we should use a WordPress plugin that is specifically designed for turning a WordPress site static, such as:

rather than rolling our own solution that will run into WordPress-specific subtleties that we will have to reinvent solutions for.

@xet7
Copy link
Member Author

xet7 commented Mar 8, 2018

From @mrdomino on July 22, 2016 21:32

Assuming that's the road we want to go down, I'm certainly willing and possibly able to make time to do it. @dwrensha what do you think?

@xet7
Copy link
Member Author

xet7 commented Mar 8, 2018

From @dwrensha on July 23, 2016 0:57

Yeah, it'd be great if we could get an existing plugin to do the hard work for us. Last time I tried to go that route, I think I ran into difficulties regarding directory structure, and maybe I also hit sqlite-vs-mysql problems. But it seems like there ought to be a way to make it work, so I encourage you to try.

@xet7
Copy link
Member Author

xet7 commented Mar 8, 2018

From @paulproteus on July 23, 2016 1:2

FWIW, I also personally think that MySQL would be a fine database for the Sandstorm WordPress package, to maximize compatibility. That's a separate topic to discuss on a separate issue perhaps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant