There is typically waaaay more than HTML driving a modern website. In particular, there is usually a great deal of dependence on third party services to render a page.
Surely it wouldn't normally be written into the HTML? Or is this actually what you normally get if you use a website builder, or get someone else to do it? (My only experience is of coding my own webpages.)
What your browser displays is HTML. So whatever you see on your screen is somehow in the HTML that's served to your browser and/or generated dynamically as you're viewing the page. The question is how this HTML is generated. This can be done in a static way as we did in the 1990s, and it's indeed how most of the main content of ublinkingeye was originally made. However, in that static content there's also in this case a number of places where dynamic content is embedded.Surely it wouldn't normally be written into the HTML? Or is this actually what you normally get if you use a website builder, or get someone else to do it? (My only experience is of coding my own webpages.)
<iframe style="width:120px;height:240px;" marginwidth="0" marginheight="0" scrolling="no" frameborder="0" src="//ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=unblinkingeye&marketplace=amazon®ion=US&placement=2880467144&asins=2880467144&linkId=bdef1605ce4d0fdbd389490cfc81aec9&show_border=false&link_opens_in_new_window=false&price_color=333333&title_color=0066c0&bg_color=ffffff">
</iframe>Well, yes. But the HTML as such really isn't the thing; that's just the stuff that shows up. What happens under the hood is where the complexity is. In part this is client-side processing that happens mostly in JavaScript, which you can trace down and dive into if you have plenty of time. But there's also generally a lot of server-side processing going on; sometimes this results in quasy-static content being served (classic PHP generated server-side, for instance), but today, most websites use 'live' content with the browser continuously interacting through something like e.g. AJAX with a server backend. The frameworks used for this can be exceedingly complex and only a small part is visible to the typical end-user (which of course is by design).There is typically waaaay more than HTML driving a modern website.
Sorry for the digression. I agree that @pentaxuser's problem is most likely related to his browser not supporting some aspect of security. I looked at the structure of the website out of curiosity, simply to see whether there was anything obvious related to security that was unique to this website. Obviously enough, I don't have any expertise. I guess certification and HTTPS are implemented at the domain level, not in the code.yeah, that's typical of badly-behaved ads on a website that's not very solidly set up to begin with. What essentially happens is that the ad JavaScript that runs on the client machine modifies the HTML that's originally served to the client. Any self-respecting webmaster would report such ads to their ad partner (amazon and/or google in this case) so they would be taken down.
Anyway, we're now in the territory of philosophizing about badly maintained websites and malicious ad systems, exacerbated possibly by weak or missing client-side security. That's a different issue from the connection problems that @pentaxuser reported.
I was doing a bit of research this afternoon and wanted to look at the above site. I tried the link in the site I was on, then tried my own bookmark and finally Googled it Everytime I got the same notice of "403 Forbidden
Has it folded and been removed ? It was sometime ago that I last tried it
Thanks
pentaxuser
I get the same result when I'm using my laptop running Win8, my desktop runs Win11 and it pops right up, no problem.
Windows 7 really doesn't have anything to do with this. Websites in general don't care what OS runs on the machine that the client uses. The risks of an outdated OS are on the client's side, not so much the server's side.
This can sometimes helps if the problem is specifically related to SSL. There's no indication here that this is the case. However, many browsers are now starting to categorically block non-SSL traffic at least on public networks.
I have had similar problems with some websites. My solution is to remove the security tag from the https: address. This is how I handle it: Click the link so it populates the address bar, then go up to the "https://***" part of the address ad edit out the "s"-- that is -- change it to "http://***" and hit the enter key. That will usually process the URL and the site will open. As near as I can tell, there are no visible side effects to doing this if you are just browsing. I'm not sure how this will affect the security if you are ordering items, or exchanging emails, etc.
Not saying this will work for your problem, but it's a simple process to test and keep in mind for future, similar problems.
GT
Those having trouble may wish to browse the Internet Archive's archive of the site:
I'd try the fix recommended by @Don_ihIs it now more likely to be the use of Google which no longer gives support for Win7 as others have suggested or something else
Hi @pentaxuser I would suggest you drop an email to the webmaster of the site. Let him/her know what you're error message is when you try to access the page. On the bottom of one of the webpages (the About page) is this link: webmaster@unblinkingeye.com Hope this helps,
Thanks but is the link to which you refer within the unblinkingeye website
Thanks koraks What you have said in the first part of your quote above is what I had intuitively thought So if it unlikely to be Win7 that is causing the problem what might it be and what might I try to fix it?
Is it now more likely to be the use of Google which no longer gives support for Win7 as others have suggested or something else
I tried this or so I think but typing in the address leaving out the "s" and entering takes me to the https which of course give me the 403 Forbidden
It seems that I cannot alter the address and get other than its https address
Maybe I am not doing it right?
pentaxuser
Thanks koraks What you have said in the first part of your quote above is what I had intuitively thought So if it unlikely to be Win7 that is causing the problem what might it be and what might I try to fix it?
Is it now more likely to be the use of Google which no longer gives support for Win7 as others have suggested or something else
I tried this or so I think but typing in the address leaving out the "s" and entering takes me to the https which of course give me the 403 Forbidden
It seems that I cannot alter the address and get other than its https address
Maybe I am not doing it right?
pentaxuser
Thanks koraks What you have said in the first part of your quote above is what I had intuitively thought So if it unlikely to be Win7 that is causing the problem what might it be and what might I try to fix it?
Is it now more likely to be the use of Google which no longer gives support for Win7 as others have suggested or something else
I tried this or so I think but typing in the address leaving out the "s" and entering takes me to the https which of course give me the 403 Forbidden
It seems that I cannot alter the address and get other than its https address
Maybe I am not doing it right?
pentaxuser
Honestly, there's no telling what may have changed on their end, your end as well as the routing in-between.
It's magic.
Honestly, there's no telling what may have changed on their end, your end as well as the routing in-between.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?