My userpage in the Toolserver webserver - Toolserver-l - lists.wikimedia.org

List overview All Threads
Download

My userpage in the Toolserver webserver

S1 replag

nightshade status

محمد الجداوي

25 Mar 2012 25 Mar '12

7:17 p.m.

Hi all, I made a HTML file named "mgedawy.htm" in order to make my userpage in the Toolserver webserver, And put the file inside the folder "* public_html/*". The problem is that i find the page i created at: http://toolserver.org/~mgedawy/mgedawy.htm instead of: http://toolserver.org/~mgedawy/ How can i solve this please?

Attachments:

attachment.htm (text/html — 733 bytes)

Reply

Show replies by date

Hersfold

25 Mar 25 Mar

7:19 p.m.

In order for the page to appear at http://toolserver.org/~mgedawy/, it needs to be titled "index.html" or "index.htm" or similar. It's the same with any web server. ---- User:Hersfold hersfoldwiki(a)gmail.com On 3/25/2012 1:17 PM, ???? ??????? wrote:

Hi all, I made a HTML file named "mgedawy.htm" in order to make my userpage in the Toolserver webserver, And put the file inside the folder "/public_html//". The problem is that i find the page i created at: http://toolserver.org/~mgedawy/mgedawy.htm <http://toolserver.org/%7Emgedawy/mgedawy.htm> instead of: http://toolserver.org/~mgedawy/ <http://toolserver.org/%7Emgedawy/> How can i solve this please? _______________________________________________ Toolserver-l mailing list (Toolserver-l(a)lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette

Reply

MZMcBride

10:51 p.m.

Hersfold wrote:

In order for the page to appear at http://toolserver.org/~mgedawy/, it needs to be titled "index.html" or "index.htm" or similar. It's the same with any web server.

Unless you override the default behavior, yes. Apache has a DirectoryIndex directive that's trivial to specify in (for example) .htaccess. I'm sure ZWS has similar functionality... somehow. MZMcBride

Reply

Platonides

26 Mar 26 Mar

12:20 a.m.

On 25/03/12 22:51, MZMcBride wrote:

Hersfold wrote:

In order for the page to appear at http://toolserver.org/~mgedawy/, it needs to be titled "index.html" or "index.htm" or similar. It's the same with any web server.

Unless you override the default behavior, yes. Apache has a DirectoryIndex directive that's trivial to specify in (for example) .htaccess. I'm sure ZWS has similar functionality... somehow.

Somehow like this? :) echo 'DirectoryIndex mgedawy.htm' > .htaccess It's the same way in ZWS as in Apache. See https://wiki.toolserver.org/view/ZWS#Directory_Listing_Directives

Reply

MZMcBride

6:27 a.m.

Platonides wrote:

On 25/03/12 22:51, MZMcBride wrote:

Hersfold wrote:

In order for the page to appear at http://toolserver.org/~mgedawy/, it needs to be titled "index.html" or "index.htm" or similar. It's the same with any web server.

Unless you override the default behavior, yes. Apache has a DirectoryIndex directive that's trivial to specify in (for example) .htaccess. I'm sure ZWS has similar functionality... somehow.

Somehow like this? :) echo 'DirectoryIndex mgedawy.htm' > .htaccess It's the same way in ZWS as in Apache. See https://wiki.toolserver.org/view/ZWS#Directory_Listing_Directives

Yeah, I saw that the documentation said that. I'm not sure if it's still true. I quickly tested earlier today and it seemed to be inaccurate info. I know ZWS has some .htaccess support (or did), but I'm not sure if it's changed (it may be dependent on a setting that got lost) or gone away or what. I think the eventual plan is to switch back to Apache. Just as soon as everyone has rewritten their rewrite rules and redirects for ZWS. MZMcBride

Reply

Tim Landscheidt

2:26 p.m.

MZMcBride <z(a)mzmcbride.com> wrote:

[...] I think the eventual plan is to switch back to Apache. Just as soon as everyone has rewritten their rewrite rules and redirects for ZWS.

BTW, my ~/public_html/.htaccess contains: | # Added by install-php on Mon Jun 20 19:17:35 UTC 2011; this enables the PHP | # wrapper so PHP scripts work. You can edit the "php" script by hand, but if | # you run install-php again, it will be overwritten. | FCGIWrapper "/home/timl/public_html/fcgi-bin/php" .php | AddHandler fcgid-script .php which seems to trigger the warnings in /var/log/http/errors (on wolfsbane): | [26/Mar/2012:12:12:41 +0000] WARN:toolserver.org:Unknown directive: fcgiwrapper | [26/Mar/2012:12:12:41 +0000] WARN:toolserver.org:Unknown handler: fcgid-script that account for about two thirds of log content. Is this still needed? Will it be needed on Apache? Should all .htaccess files be changed globally by the admins in the meantime? Other log file fillers are: | WARN:toolserver.org:Unknown directive: addcharset | WARN:toolserver.org:Unknown directive: addoutputfilterbytype which I couldn't grep in any user .htaccess files and: | WARN:toolserver.org:Unknown directive: rewriteengine | WARN:toolserver.org:Unknown directive: rewriterule which are ubiquitous, but fall under your observation above. Tim

Reply

Platonides

9:14 p.m.

On 26/03/12 14:26, Tim Landscheidt wrote:

MZMcBride <z(a)mzmcbride.com> wrote: > [...] > I think the eventual plan is to switch back to Apache. Just as soon as > everyone has rewritten their rewrite rules and redirects for ZWS.

That doesn't seem consistent with the apache testing being down...

BTW, my ~/public_html/.htaccess contains: | # Added by install-php on Mon Jun 20 19:17:35 UTC 2011; this enables the PHP | # wrapper so PHP scripts work. You can edit the "php" script by hand, but if | # you run install-php again, it will be overwritten. | FCGIWrapper "/home/timl/public_html/fcgi-bin/php" .php | AddHandler fcgid-script .php which seems to trigger the warnings in /var/log/http/errors (on wolfsbane): | [26/Mar/2012:12:12:41 +0000] WARN:toolserver.org:Unknown directive: fcgiwrapper | [26/Mar/2012:12:12:41 +0000] WARN:toolserver.org:Unknown handler: fcgid-script that account for about two thirds of log content. Is this still needed?

It is installed by install-php, as instructed by https://wiki.toolserver.org/view/Apache_testing ZWS is not using it, but required by Apache (for a running php). So there is a conflict there, in that one complains of the code placed for the other. If they can't be put into server-specific sections, they should at least ignore themselves.

Will it be needed on Apache? Should all .htaccess files be changed globally by the admins in the meantime?

I'm not sure why it needs a FCGIWrapper per user. Maybe for setting the uid, or to avoid reusing a fcgid under different credentials. Seems something better configured in a global way.

Other log file fillers are: | WARN:toolserver.org:Unknown directive: addcharset | WARN:toolserver.org:Unknown directive: addoutputfilterbytype which I couldn't grep in any user .htaccess files and:

I see an AddCharset at ~bryan/public_html/{stats/,}.htaccess, ~cbm/public_html/data/.htaccess and ~holek/public_html/misc/autoupdate/.htaccess. The later also including a AddOutputFilterByType (it seems way too complex for a simple toolserver tool)

| WARN:toolserver.org:Unknown directive: rewriteengine | WARN:toolserver.org:Unknown directive: rewriterule which are ubiquitous, but fall under your observation above. Tim

Those are rules for mod_rewrite, which is explicitely documented as NOT working on ZWS.

Reply

4413

days inactive

4414

days old

toolserver-l@lists.wikimedia.org

Manage subscription

6 comments

5 participants

tags (0)

participants (5)

Hersfold
MZMcBride
Platonides
Tim Landscheidt
محمد الجداوي