main.css

Hi All,

I called an external stylesheet main.css, created the html files and
checked them locally OK. I uploaded everything to the server. When I
checked it, the connection kept crashing. I finally figured out that
the connection was freezing up every time I called index.html. I
changed the name of the stylesheet and changed the links, and I no
longer had the problem. Doing a Google search turned up nothing, can
anyone give me any incite?

Andy

"There would be a lot more civility in this world if people
didn't take that as an invitation to walk all over you"
- (Calvin and Hobbes)

and then andy johnson said:

I called an external stylesheet main.css, created the html files and
checked them locally OK. I uploaded everything to the server. When I
checked it, the connection kept crashing.

You don't mean crashing. Crashing means the program stopped responding to
input. You mean the stylesheet was not included.

I finally figured out that
the connection was freezing up every time I called index.html. I
changed the name of the stylesheet and changed the links, and I no
longer had the problem.

can anyone give me any incite?
You should use a spell chequer :-)

An "absolute url" (complete address) looks like:
http://www.example.com/path/style.css

If you use a "relative url", which does not start http:, then it must be
"resolved" with the address of the document*. What has been hapening is
that how the files are aranged locally, the relative url resolves correctly
to the url (address) of the stylesheet locally, but how they are arranged
on the server, it does not.

If the For example:

Absolute url:
http://www.example.com/
Relative url:
style.css
Resolves to:
http://www.example.com/style.css

Absolute url:
http://www.example.com/index.html
Relative url:
style.css
Resolves to:
http://www.example.com/style.css

Absolute url:
http://www.example.com/path/
Relative url:
style.css
Resolves to:
http://www.example.com/path/style.css

Absolute url:
http://www.example.com/index.html
Relative url:
dir/style.css
Resolves to:
http://www.example.com/dir/style.css

Absolute url:
http://www.example.com/path/
Relative url:
dir/style.css
Resolves to:
http://www.example.com/path/dir/style.css

Absolute url:
http://www.example.com/index.html
Relative url:
/style.css
Resolves to:
http://www.example.com/style.css

Absolute url:
http://www.example.com/path/
Relative url:
/style.css
Resolves to:
http://www.example.com/style.css

Absolute url:
http://www.example.com/path/more/index.html
Relative url:
/style.css
Resolves to:
http://www.example.com/style.css

Absolute url:
http://www.example.com/index.html
Relative url:
style.css
Resolves to:
http://www.example.com/style.css

Absolute url:
http://www.example.com/path/
Relative url:
.../style.css
Resolves to:
http://www.example.com/style.css

Absolute url:
http://www.example.com/path/more/index.html
Relative url:
.../style.css
Resolves to:
http://www.example.com/path/style.css

You can do a google search for "resolve a relative url".

* if you use a <base> element the href attribute of this will be used
instead of the address of the document.

"There would be a lot more civility in this world if people
didn't take that as an invitation to walk all over you"
- (Calvin and Hobbes)

Please correctly delimit your signiture with newline-dash-dash-space-newline
or remove it.

viza <none (AT) example (DOT) invalid> wrote

and then andy johnson said:

I called an external stylesheet main.css, created the html files and
checked them locally OK. I uploaded everything to the server. When I
checked it, the connection kept crashing.

You don't mean crashing. Crashing means the program stopped responding to
input. You mean the stylesheet was not included.

I finally figured out that
the connection was freezing up every time I called index.html. I
changed the name of the stylesheet and changed the links, and I no
longer had the problem.

can anyone give me any incite?
You should use a spell chequer :-)

An "absolute url" (complete address) looks like:
http://www.example.com/path/style.css

If you use a "relative url", which does not start http:, then it must be
"resolved" with the address of the document*. What has been hapening is
that how the files are aranged locally, the relative url resolves correctly
to the url (address) of the stylesheet locally, but how they are arranged
on the server, it does not.

If the For example:

Absolute url:
http://www.example.com/
Relative url:
style.css
Resolves to:
http://www.example.com/style.css

Absolute url:
http://www.example.com/index.html
Relative url:
style.css
Resolves to:
http://www.example.com/style.css

Absolute url:
http://www.example.com/path/
Relative url:
style.css
Resolves to:
http://www.example.com/path/style.css

Absolute url:
http://www.example.com/index.html
Relative url:
dir/style.css
Resolves to:
http://www.example.com/dir/style.css

Absolute url:
http://www.example.com/path/
Relative url:
dir/style.css
Resolves to:
http://www.example.com/path/dir/style.css

Absolute url:
http://www.example.com/index.html
Relative url:
/style.css
Resolves to:
http://www.example.com/style.css

Absolute url:
http://www.example.com/path/
Relative url:
/style.css
Resolves to:
http://www.example.com/style.css

Absolute url:
http://www.example.com/path/more/index.html
Relative url:
/style.css
Resolves to:
http://www.example.com/style.css

Absolute url:
http://www.example.com/index.html
Relative url:
style.css
Resolves to:
http://www.example.com/style.css

Absolute url:
http://www.example.com/path/
Relative url:
../style.css
Resolves to:
http://www.example.com/style.css

Absolute url:
http://www.example.com/path/more/index.html
Relative url:
../style.css
Resolves to:
http://www.example.com/path/style.css

You can do a google search for "resolve a relative url".

* if you use a <base> element the href attribute of this will be used
instead of the address of the document.

"There would be a lot more civility in this world if people
didn't take that as an invitation to walk all over you"
- (Calvin and Hobbes)

Please correctly delimit your signiture with newline-dash-dash-space-newline
or remove it.

You should use a spell chequer :-)

On Thu, 14 Aug 2003 22:20:33 GMT, Brian
<usenet1 (AT) mangymutt (DOT) com.invalid-remove-this-part> wrote:

andy johnson wrote:

I called an external stylesheet main.css, created the html files and
checked them locally OK. I uploaded everything to the server. When I
checked it, the connection kept crashing. I finally figured out that
the connection was freezing up every time I called index.html. I
changed the name of the stylesheet and changed the links, and I no

url?

The URL is http://www.oawater.com/ but my question was just generally
if main .css was a no-no. Doing a google search didn't turn up
anything conclusive, and the site is being put up with
oawstylesheet.css just fine. I just seemed strange that it would
freeze the connection that way. The style sheet name change fixed it.

Andy

"There would be a lot more civility in this world if people
didn't take that as an invitation to walk all over you"
- (Calvin and Hobbes)

andy johnson / 2003-08-16 01:52:

On Fri, 15 Aug 2003 15:30:16 GMT, Brian
usenet1 (AT) mangymutt (DOT) com.invalid-remove-this-part> wrote:

meta http-equiv="pics-label" content='(pics-1.1
"http://www.icra.org/ratingsv02.html" comment "ICRAonline EN v2.0" l
gen true for "http://www.oawater.com" r (nz 1 vz 1 lz 1 oz 1 cz 1)
"http://www.rsac.org/ratingsv01.html" l gen true for
"http://www.oawater.com" r (n 0 s 0 v 0 l 0))'

What is the "pics-label" thing all about?

Don't know, this is just the code that is on the email to put in the
head of my files.

Yeah, it'll be /very/ meaningful, indeed.

IIRC pics-label is supposed to describe page content for filtering
software (but I guess everybody just tells that the content is
"suitable for everybody" here, including p0rn sites). The original
idea was probably that sites like "disney" could claim that they
have content suitable for small childrends?

If somebody has pointers to describe what all those flags and
numbers are supposed to mean, please, throw us a bone.

--
Mikko