Web server headers

**reynolds** · 3 December 2004, 17:55

re

Bloody ell it's like a ghost town in here. Has everyone packed up and gone to India?

**AtW** · 3 December 2004, 20:33

be more specific

there are more request types done by webservers than HEAD/GET/POST. If you meant the latter, then lack of content-type is likely to be fatal for most browsers.

**AtW** · 4 December 2004, 00:02

time

It took you just above 4 hours to repeat your post, yet, 5 hours after response was posted you still not around.

Amateurs these days :rolleyes

**reynolds** · 4 December 2004, 18:16

re

Cheers mate. I think if the content-type isn't sent then the save as dialog will pop up.

**nobody here but us chickens** · 4 December 2004, 18:33

Re: re

Its all in the spec - http.

google for it.

**reynolds** · 4 December 2004, 20:15

re

Is there a spec for what constitutes a valid href tag?

I mean some browsers like stuff like:

<a href=>>

But surely it's not valid? Likewise with certain filenames.

I've looked at some RFC's but no spec.

**AtW** · 4 December 2004, 21:46

valid

<a href=>> -- technically its not valid, but good browsers will ignore any >'s after tag was closed (after first >).

Here: http://www.w3.org/TR/REC-html40/

Links specifically: http://www.w3.org/TR/REC-html40/struct/links.html

If you want to make browser prompt to save item then you should NOT avoid using content-type and instead try appropriate type for your content, and if its not define then browser will prompt used to save it.

Web server headers