Hacker News Reader

Hacker News

Comment by retox | Hacker News Reader

Full thread

retox

A handful of sites will present the subscribers view of the page if you put a dot after the tld part of the url, i.e.

https://site.com./1235/article

Those behind Cloudflare don't seem to be vulnerable to this though.

I've emailed the sites I've found where this works and none of them have fixed it after a year.

View on HN

>I've emailed the sites I've found where this works

Why?

Can't speak for OP but I think I would be annoyed if I was paying a subscription and I found out I could get around it with a simple `.` because of developer incompetence.

If you are paying for a subscription then hopefully you do it to support the publication and find their work useful, and not because of a nag banner.

> to support the publication and find their work useful, and not because of a nag banner.

Unfortunately they kind of go hand in hand these days!

People don't pay for free stuff, even if they like it. People are however lazy, and many would pay to not have to put a dot in the URL every time.

Good that you spoke for yourself.

Why would this work? I know FQDNs sometimes require specifying a period at the end, and browsers seem to accept it as well, but I wonder why this would affect some frameworks' displayed content. Normally a site would rely on a cookie to maintain logged-in status, and that shouldn't be affected by the request URL.

Maybe some backend concession to allow viewing the article on hostnames/uris that are meant for internal use, partner sharing sites, etc? Like an if/then that checks the origin hostname?

Maybe Javascript or backend mistake in matching the domain name - most people don't know that domain names can end with a final dot.

> I've emailed the sites I've found where this works and none of them have fixed it after a year.

Guess it's a feature then and not a bug.

Maybe some kind of common mistake when writing a pattern match

Reply on news.ycombinator.com