Davide Bianchi wrote:
Whenever I try to see that URL, I get a 302 redirecting me to /v2/,
maybe that is the problem. How about setting THAT as your DocumentRoot
instead of plain-old /var/www/htdocs ?
Tried it, but doesn't help.
Sorry, let's take a break on this problem. The future and addition
Davide Bianchi wrote:
Yes, exactly, it is a PUBLICLY ACCESSIBLE url, and the fast way to test
something is just to look at it. So why hiding it?
Okay, no problem. If this can be of any help?
http://coit.uniten.edu.my
We are running the old version now, to have the current content accessible.
Davide Bianchi wrote:
What is 'foo.bar.edu.my'?
I simply didn't want to invite too many people; it is a publicly
accessible FQDN.
And what is the httpd.conf BEFORE the
changes?
I was afraid, it might be too long. Now it is attached.
Uwe
# $OpenBSD: httpd.conf,v 1.19 2006/02/22 15
I have been working on this, reading the documentation, googled, but
haven't found the solution:
I administrate foo.bar.edu.my. Until now, it is one CMS. In future, we
want to use more, so I tried vhosts.
This is what I added to hhtpd.conf:
diff httpd.conf.novirtual httpd.conf
On Mon, 28 Nov 2005 14:54:49 +0100, Joost de Heer wrote:
> IndexOptions +NameWidth=*
My excuses for asking this simple question.
My only excuse: It seems badly documented. I tried Google once I got your
answer, and there does not seem to be a concise description.
Again, thanks and my excuses !
When displaying files as lists, I found some small differences at the
widths between 1.3 and 2.0. So do my users, and ask me to set / change the
width of the columns to make more characters of the filenames show. I
found a similar request in the archives, more than 3 years ago. There was
no answer
One of my users had functional CSS on 2.0; but on 1.3 all pages simply
show 'blank'.
When I remove his index.html, of course the files become visible.
css is - of course - in the untouched mime.types
My 2 questions:
1. Has there been a change in handling CSS from 1.3 to 2.0 ?
2. (I'm pretty blan
