On again Off again 404 errors

I’m experiencing instability on one of my pages and getting frequent 404 errors. The address is:

https://semicodin.infinityfreeapp.com/origin/shape-outside_(URL)_01.html

I’m wondering if the all caps URL or the parenthesis is an issue although it shouldn’t be because I never had an issue with it on my old site. I notice a number of people also getting 404 errors. What’s happening? work on the drive?

In short, you have to be careful about capital letters here, as our servers are case sensitive.

And yes, avoid special characters as much as possible. Don’t use spaces at all.

3 Likes

I see. I’ll rename the file.

It’s no good. I renamed the file https://semicodin.infinityfreeapp.com/origin/shape-outside-url-01.html

and still I get 404 errors. The only character even remotely controversial is the hyphens but if you’re telling me I can’t even use hyphens then we’re going to have a very short relationship indeed. Hyphens are universally recognized on any commercial news site to name just one. You can’t handle hyphens? Wow.

Also, I’ve had this particular file display perfectly on three separate browsers on my former site, but on your server it cannot recognize the shape-outside property: this is a CSS method for wrapping text around an image. On your server it isn’t working (and that’s when I can get it to display after a direct entry on the address bar). I may have to use this site exclusively for PHP and put all my html files back on my former host’s site. :roll_eyes:

@semicodin I have no issue loading the page

maybe clearing the browser cache might help ?

hyphens are not a problem on this hosting feel free to use them :+1:

2 Likes

Of course we can handle hyphens, and we can handle special characters and spaces. The only reason why did I tell you to remove special characters is that most people failed to handle them.

It’s safe to assume that nobody is gonna screw up hyphens, so it’s good.

I don’t know what your issue really is though, CSS class not working is no where near 404 errors. What are you seeing right now and what did you expected to see?

3 Likes

The text is supposed to wrap around the image and it doesn’t. Or at least, it doesn’t when I can get it to display. It’s alright Frank I can limit my files to PHP here although I was hoping to have one home for everything. No problem.

If you have CSS problems, then please blame your browser for this. Hosting is simply 100% unrelated to frontend styling.

Please try clear your browser cache or use incognito mode.

3 Likes

Oh I cleared everything. Here, just for the record, is how it is supposed to display. That’s with the original spelling of the file. Perhaps they’re on ASP. No great deal. If it works for all of your subscribers and they’re satisfied that’s all that matters.

Well, your site here also displays exactly what it displays on the other site.

2 Likes

It didn’t wrap for me on two browsers (Chrome, Vivaldi).

Well, it wraps for me on Chrome.

Also, nekoweb is static.
What’s more, your page is also static, which means PHP or ASP doesn’t matter at all here.

Please post screenshots about what you actually sees, not just describe them. Also are you sure that the browser cache is actually cleared, not that just you think that it’s cleared?

2 Likes

I’m content to leave my HTML on Neko; having to be limited by my file names is a huge turnoff Frank. I’ll do it on PHP but I don’t want to have to with my html. Yeah I cleared everything.

ANI bSHRUG

Well, I’ve told you there’s simply nothing to do with the server side languages. Only if you shared a screenshot may we better tell what’s the true problem.

2 Likes

Alright. Let me upload it then.

Here it is on Vivaldi:

And I get a 404 on Chrome:

Calling it a night . . .

1 Like

Yes, what’s you see is exactly what I have said before: you think that you have cleared the cache, but in reality, it isn’t, because you probably have only cleared the cache of the 404 page, not the actual page.

Which means that now you should follow the guide I gave you earlier to fully empty everything in your browser.

4 Likes

Both URLs (the lowercase and dashes, and the one with underscores, braces and capital leters) show the exact same content to me.

Our servers can handle basically any characters in file and directory names. Basically anything goes. However, officially URLs only support a small subset of characters: letters, numbers, dashes, underscores, dots and tilde. Any other character can be used, but need to be encoded. And this is usually where problems start to arise, because if you don’t handle the encoding yourself properly in your website, you’re at the mercy of browsers to fix your mistakes for you. And different browsers behave differently.

Add case sensitive file and directory names to the mix, and you can see why we recommend to stick to lowercase letters only and avoid special characters. Not because our hosting doesn’t support them, but because it’s way too easy to make mistakes.

So as to why you may be seeing a 404 URL, I can think of various reasons:

  • The 404 page may be cached in your website. Please clear your browser cache or try to open the page in Incognito Mode, which circumvents all caches in your browser.
  • Your browser may be mis-encoding the URL with the special characters. That’s not a hosting issue, that’s a browser issue.
  • Are you trying to access the page by going to the URL directly or by clicking a link from another page? If so, the link on the other page may not have encoding the URL correctly. That’s also not a hosting issue, but a website code issue.
4 Likes