• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers

Jeffrey Friedl plugin page gives 404 Not Found erroe

Community Beginner ,
Nov 29, 2022 Nov 29, 2022

Copy link to clipboard

Copied

I need to re-register my jf plugins since the last LR update. When I try to go to his page I get a 404 Not Found error. Anyone know if this is a temporary glitch or is his stuff no longer available?

TOPICS
Windows

Views

339

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Nov 29, 2022 Nov 29, 2022

Copy link to clipboard

Copied

It's probably temporary or intermitent as I've just accessed it via http://regex.info/blog/lightroom-goodies

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Dec 07, 2022 Dec 07, 2022

Copy link to clipboard

Copied

I was not able to get  on using firefox.I was finally able to get on using chrome, but it was not straight forward. I think it may have something to with my security settings and security plug-ins. Even with chrome it tells me that it is "not a secure site."

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Dec 07, 2022 Dec 07, 2022

Copy link to clipboard

Copied

LATEST

I've able to access it his plugins via Chrome, Firefox, and Safari on Mac OS, without any changes to the default security settings (I think) and no third-party security software:

http://regex.info/blog/lightroom-goodies 

 

Your problems may be related to his now atypical server structure, in which  "http://path" doesn't access the same content as "https://path":

 

"This is the HTTPS server at Jeffrey's machine; Jeffrey's public-facing content is on his HTTP server: http://regex.info/.

 

"(My HTTP and HTTPS trees have been separate for decades; a browser feature that automatically assumes that all HTTP servers have an identical HTTPS server is making some very big, and in this case, wrong, assumptions.)"

 

His content is all accessed via HTTP, not HTTPS, which is why browsers flag the site as "not secure", though in practice, since it serves static, non-personalized content, it's as secure as most other sites.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines