You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @davideast. Thanks for this great project. We use hnpwa-api (with a caching proxy on top of it) for nuxt/hackernews. Everything is fine and smooth. The only problem is that almost all website testers including webpagetest and PageSpeed Insights detect API calls to URLs ending with .json as static asset thus reducing final points even when adding cache headers!
I wonder if is it possible to make changes to provide URLs without .json extension or not? We can do such rewrites for nuxt-hackernews only but I think it may be useful for others too.
Hey @pi0! Thanks for the kind words, and thank you for Nuxt!
This is definitely possible through the firebase.json configuration. There's a few solutions here. I can make a change to the API, although it would be a breaking change to the v0 API. Or, if you're hosting your own server, you can re-write the .json calls to use "cleanUrls" so there's no extension.
Thanks, David for the answer. I'm proxy-passing requests down to the to the api.hnpwa.com and for sure both rewriting URLs and hosting are perfect ideas.
BTW for the change, Can't we add more routes without .json extension to the /v0`?
Hey @davideast. Thanks for this great project. We use hnpwa-api (with a caching proxy on top of it) for nuxt/hackernews. Everything is fine and smooth. The only problem is that almost all website testers including webpagetest and PageSpeed Insights detect API calls to URLs ending with
.json
as static asset thus reducing final points even when adding cache headers!I wonder if is it possible to make changes to provide URLs without
.json
extension or not? We can do such rewrites for nuxt-hackernews only but I think it may be useful for others too.Deployed versions:
SSR: https://hn.nuxtjs.org
SPA: https://hn-spa.nuxtjs.org
The text was updated successfully, but these errors were encountered: