News for hackers. Stuff that matters.
Re:Lcl.host: fast, easy HTTPS in your local dev environment by JimDabell on Wednesday March 20, 2024 @11:39AM (#39768128)
Warning: This checks if it’s running the latest version and refuses to run if it isn’t up to date. They just released v0.0.16 15 minutes ago and the update hasn’t hit Homebrew yet, so it has completely disabled itself and won’t run. There doesn’t seem to be any option to skip the version check.

So don’t use this unless you don’t mind it breaking randomly whenever there’s an update.

Re:Lcl.host: fast, easy HTTPS in your local dev environment by benburkert on Wednesday March 20, 2024 @12:20PM (#39768685)
Sorry about that, we're working on switching this to a warning and not an error, that slipped by us before release. After the next update, it will only show a warning if you're not on the latest release.
Re:Lcl.host: fast, easy HTTPS in your local dev environment by benburkert on Wednesday March 20, 2024 @01:17PM (#39769474)
We just released a fix for the version error, this will be the last one you see, we promise!
Re:Lcl.host: fast, easy HTTPS in your local dev environment by fbdab103 on Wednesday March 20, 2024 @08:13PM (#39773590)
How about being able to disable the check entirely? I really dislike tools phoning home unless asked.
Re:Lcl.host: fast, easy HTTPS in your local dev environment by JimDabell on Thursday March 21, 2024 @02:34AM (#39775444)
Thanks. The upgrade command v0.0.15 gives didn’t work for me. In fact the only method I found that would successfully update was to uninstall it, then untap your tap, then reinstall.

Also, I echo the other people saying that the typeface you chose for the website is very difficult to read.

Re:Lcl.host: fast, easy HTTPS in your local dev environment by mholt on Wednesday March 20, 2024 @11:45AM (#39768204)
When I first announced Caddy, our website downloaded everything as .gz due to high traffic load -- a lesson I learned very quickly and a mistake I never made again.

This probably falls in the same boat. :)

Re:Lcl.host: fast, easy HTTPS in your local dev environment by emi2k01 on Wednesday March 20, 2024 @11:50AM (#39768262)
Sorry, maybe it's too early in the day but I don't get what the lesson was. Could you explain?
Re:Lcl.host: fast, easy HTTPS in your local dev environment by orliesaurus on Wednesday March 20, 2024 @12:02PM (#39768425)
(IMHO) the lesson is that sometimes you're excited to tell the world about what you built, that you forget about some "other stuff"

i.e. I don't think that the authors of this tool wanted to have developers be forced to use the latest version of their tool.

It's probably that they didn't think about it when they wrote the code, but now they know and hopefully this gets fixed in the next release?

Re:Lcl.host: fast, easy HTTPS in your local dev environment by hackmiester on Wednesday March 20, 2024 @12:08PM (#39768509)
I just don't understand what the thing about "downloading everything as .gz" means. It's not like a gz is a rare file format, it seems like a totally reasonable format to download something in.
Re:Lcl.host: fast, easy HTTPS in your local dev environment by wolfgang42 on Wednesday March 20, 2024 @12:19PM (#39768673)
Having once made a similar mistake myself, I assume what they mean is that it was downloading everything as a .gz—that is, the browser was asking users “where would you like to save index.html.gz?” instead of showing the homepage. (This happens when you precompress a static site for performance, but forget to tell the server that gzip should be negotiated as a Content-Encoding instead of a Content-Type.)
Re:Lcl.host: fast, easy HTTPS in your local dev environment by mholt on Wednesday March 20, 2024 @12:18PM (#39768653)
To clarify, every page load (.html file) was downloaded as a .gz file instead of being served as an HTML file and displayed as a web page in the browser.
Re:Lcl.host: fast, easy HTTPS in your local dev environment by mholt on Wednesday March 20, 2024 @12:07PM (#39768491)
Yeah, exactly. A lot goes into shipping, and sometimes things like this can be overlooked, especially on a small team that needs to deliver broad platform support right out of the gate.

There are some bugs that are just hard to find until they're out there.

Re:Lcl.host: fast, easy HTTPS in your local dev environment by thomasfromcdnjs on Wednesday March 20, 2024 @11:38PM (#39774700)
When we first release cdnjs.com we used tools to check if the DNS had fully propagated... but it hadn't. The shame of a cdn being down in several places across the globe.
Re:Lcl.host: fast, easy HTTPS in your local dev environment by jollyllama on Wednesday March 20, 2024 @11:48AM (#39768232)
Gross. Thanks for the heads up!
Re:Lcl.host: fast, easy HTTPS in your local dev environment by apgwoz on Wednesday March 20, 2024 @03:04PM (#39770675)
Not affiliated with them, but it seems this was a mistake. https://news.ycombinator.com/item?id=39768685 -- maybe give it another shot?
Re:Lcl.host: fast, easy HTTPS in your local dev environment by pmarreck on Wednesday March 20, 2024 @03:33PM (#39771041)
They fixed this. It's now a warning.
Re:Lcl.host: fast, easy HTTPS in your local dev environment by hipadev23 on Wednesday March 20, 2024 @04:27PM (#39771633)
That's an absurd tactic I've not seen since last time I used Firefox.
Re:Lcl.host: fast, easy HTTPS in your local dev environment by yoavm on Wednesday March 20, 2024 @06:07PM (#39772578)
you're completely free to run firefox from 5 years ago and it will not refuse to run.
Re:Lcl.host: fast, easy HTTPS in your local dev environment by cookiengineer on Wednesday March 20, 2024 @09:27PM (#39774039)
No, you are not.

Mozilla bricked SSL certificates that are mandatory for everything, including Browser Extensions.

There is a flag for about:config to unbrick it. Problem is though, that this lasts less than a second because of the remote settings service running in a loop. If you block that services domain with a host firewall (like opensnitch), Firefox will do an endless for loop using 100% CPU load trying to request the shavar and other services domains.

So, effectively, you cannot run an old Firefox version, and especially not a version that uses the old bundled mozilla certificate (which is all provided download variants).

That's what the previous commenter was (likely) referring to.

Re:Lcl.host: fast, easy HTTPS in your local dev environment by yoavm on Thursday March 21, 2024 @03:09AM (#39775583)
Just for the fun I went to https://ftp.mozilla.org/pub/firefox/releases/53.0/linux-x86_... and downloaded Firefox 53 from 2017.

Font are ugly but it loaded HN just fine.

Re:Lcl.host: fast, easy HTTPS in your local dev environment by cookiengineer on Thursday March 21, 2024 @05:07AM (#39776271)
> you're completely free to run firefox from 5 years ago

> Firefox 53 from 2017

not the same. I was talking about post-quantum Firefox releases, which added the mentioned dependencies on Mozilla's SSL certificate.

(The grandparent's comment was also about post-quantum, obviously)

Re:Lcl.host: fast, easy HTTPS in your local dev environment by yoavm on Thursday March 21, 2024 @05:56AM (#39776617)
The grandparent post is about some malicious tactic used by Mozilla to prevent you from using old Firefox releases. I think it's pretty clear that there isn't such intent - if there was, the very least Mozilla would have done is preventing you from downloading old versions from their own servers. Having a few specific releases that broke over time doesn't mean anyone is trying to stop you from using an older version of Firefox. It's basically called software.
Re:Lcl.host: fast, easy HTTPS in your local dev environment by cookiengineer on Thursday March 21, 2024 @06:52AM (#39776978)
> Having a few specific releases that broke over time doesn't mean anyone is trying to stop you from using an older version of Firefox.

Snakeoil certificates in Enterprise licensing might disagree with this statement, which in my opinion is pretty identical to Mozilla's approach to have control over "who is allowed to use when" of their software.

It's also not a few specific releases over time, it's all releases after Browser Extension signatures were introduced as being mandatory, which made the rest of the Browser rely heavily on their certificate management servers.

I'm not saying it's malicious intent, what I am saying is that this could've been implemented in a much better manner, which wouldn't rely on a centralized certificate signing service.

Re:Lcl.host: fast, easy HTTPS in your local dev environment by btreecat on Thursday March 21, 2024 @07:50AM (#39777379)
Yeah they don't _have to require SSL_ but I think we can agree that is a worse thing given the benefits of securing extensions and validation of the server hosting them