Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

1 votes

'IP.Board' index.html Error Messages

Started by Con, Apr 29 2012 11:43 PM

Please log in to reply

5 replies to this topic

#1 Con

XR3X

Members
1,581 posts

Posted 29 April 2012 - 11:43 PM

There are quite a few static index.html files with error messages like the following:

<html>
<head><title>IP.Board - Bulletin Board System</title></head>
<body>
<h1>403: IP.Board -&gt; Forbidden</h1>
<hr>
You have reached this page in error, please use your back button to return to the forum.
<hr>
<a href="http://www.invisionpower.com">IP.Board</a>
</body>
</html>

I suggest either (i) making the message universally alterable, e.g. via a language bit, or (ii) implementing a more generic error message that does not suggest any specific site (e.g. invisionpower.com) or software (e.g. IP.Board, bulletin board, forum).

AlexJ, CallieJo and Marcher Technologies like this

Back to top

#2 Marcher Technologies

$life=FALSE;$code=TRUE;$time--;

+Clients
11,164 posts

Posted 29 April 2012 - 11:51 PM

guilty of using similar in apps.
agree needs to be handled far better in the core, as such lends itself to us handling it better.

Con likes this

My Modifications

Back to top

#3 Michael

Meet Jay

+Clients
18,854 posts

Posted 30 April 2012 - 06:39 AM

Those files will only ever be seen by those accessing folders without entering a file name, it's common practice in web apps to put index.html files out in each folder that you don't want people to be able to browse.

I don't believe it would be possible to make them customizable, they'd all need to be writable to do that, meaning you'd have to set their CHMOD to 777 on all 597 of them in the current version of IP.Board.

Con likes this

My Stuff: My Forum · My Resources · My Tutorials
Contact Me: Email · Facebook · Twitter · Google+
Follow Invision Focus: On Facebook · On Twitter

Back to top

#4 bfarber

RBT-KS

IPS Management
27,073 posts

Posted 30 April 2012 - 09:26 AM

They are static files and won't be editable via the ACP, language system, etc. Realistically, we don't even want to have to include them - sadly, not everyone understands how to configure their servers so that they're not needed.

AlexJ, Marcher Technologies and Con like this

Brandon Farber
Developer / Senior Support

If it sounds like fun, it's not allowed on the bus!

Invision Power Services, Inc.

Back to top

#5 CallieJo

Advanced Member

+Clients
309 posts

Posted 30 April 2012 - 02:08 PM

I ran into those, too. At one time, I went through all the folders and replaced those with blank index files like other programmers actually do for their scripts. Unfortunately, when I upgraded I forgot to do it again. Just like I forget to replace the meta image and end up with an IPB image.

Personally, I don't need index files in all the folders as I have the proper settings on my server to handle directory listings. But I understand the need as a precaution for those who don't.

However, I strongly believe that the index files should be blank. There is no need to mention the platform used. Especially when some of us paid to keep branding off the front-end. Just MHO.

Con likes this

All my old posts are under a guest account.
Please help support ideas:

Next Step After Registration / Profile Permissions / Calendar / User Portal / Comment Notifications / Blog Themes / Better Profiles / Post Rating

Back to top

#6 Con

XR3X

Members
1,581 posts

Posted 30 April 2012 - 02:26 PM

They are static files and won't be editable via the ACP, language system, etc. Realistically, we don't even want to have to include them - sadly, not everyone understands how to configure their servers so that they're not needed.

I agree, and it's not always a viable option either.

Given that they should remain static and non-customizable via a universal switch, I guess that suggestion ii (a more generic error message) or, like CallieJo suggested, a blank file (which I've seen implemented elsewhere - e.g. in the Gallery app) would be more feasible.

But as they aren't run into much, etc., obviously it's not a big deal. Just something to consider when you've fixed some of the bigger issues up and are twiddling your thumbs looking for new things to fix.