- From: kizzume <kizzume@gmail.com>
- Date: Fri, 28 Sep 2007 03:00:29 -0700 (PDT)
- To: www-svg@w3.org
Thank you very much for such a verbose response. That was extremely helpful. I guess sometimes I just need to read something in several different ways to get it in my thick skull. Unfortunately, I already made a request which was worded in an "I have no idea what I'm talking about and I admit it" sort of manner before reading this description, but I think they'll understand just out of svg and mime type being metioned. Hopefully. ;) Thanks again for such a verbose response. :) Rick-2 wrote: > > > On 9/28/07, kizzume <kizzume@gmail.com> wrote: >> >> >> Okay, that's starting to make some more sense. Somewhat. If the >> filename >> has no meaning, then how does any file get recognized as anything? No, I >> guess I'm more confused than ever now. > > Consider this, if you are generating dynamic content, there is no > file. How does the browser know what it is? > > The content header. > > Actually, in the case of files, mime types are used by the browser to > look at the file extention and report to the browser what is coming in > the content header. In the case of dynamic content, the server > program that generates the content knows what the content is, it > should, it's generating it, so it sets the content header itself. You > don't see the content header because it isn't part of the document, it > is the header that tells the client what kind of document is coming so > it can decide if it will even accept it in the first place, and if so, > what to do with it. You want it to display an SVG image, so the > client has to know that one is coming. > > The bottom line is that the server does look at the file extension for > static documents, then uses the mime type to determine what the > content is. > > The svg mime type is image/svg+xml, this is what is set in the content > header, what is set in the mime types table is this: > > image/svg+xml svg svgz > > What are svg and svgz? File extensions. The mime type that everyone > keeps telling you to get set is how the server translates the file > extension to a document type. But if it isn't there it can't. If you > create a new kind of content and create a new plugin for a client to > deal with it, you have to create a new mime type so the server can > translate the file extension to a document type and tell the client > what is coming. If you want the world to start using your fabulous > new content, you register the mime type so that everyone else can use > it. > > If it isn't there, the server uses the default, which is text. > > This is all low level server to client negotiation stuff that you > shouldn't have to worry about unless you are generating dynamic > content. In fact, you don't have to worry about it, or even read a > mime types for dummies book, just get the mime type set and the > problem will go away. > >> How can a setting on the server tell a browser what type of files are on >> that server? Is this mime type thing a file? If it's a setting--how >> does >> it work--how does it decide what TYPES of files are on the server? Is >> this >> some sort of database or something associated with each file, checking to >> see what type it is or something? Is it like the old filing sytem that >> used >> to be on MacOS9 and earlier? The more I look into this, the more >> confused >> I'm getting. >> >> Is there a "mime types for dummies" sort of faq I could look at? >> >> Sorry for my confusion--but, I'm confused. >> >> Thanks for the help. >> >> >> Oliver Hunt-2 wrote: >> > >> > >> >> Why can't files just be used as files? I guess I just don't >> >> understand--at >> >> all. A file isn't a file unless there's something on the server to >> >> tell it >> >> that it's a certain type of file? Why is that necessary? It goes >> >> right >> >> over my head, and since I really don't understand what I'd be >> >> asking the >> >> host, I'm going to have to refrain until I do understand. >> > >> > The mime type (or media type) tells the browser what the type of the >> > file is, the name has *no* meaning, all that matters is what the >> > browser is told. >> > >> >> >> >> "Yes, I'm calling because I want you to change the mime type to be >> >> correct. >> >> No, I don't really know what that means, but I need you to do it." >> > You should be able to say that their server isn't reporting the >> > correct mimetype for svg files, they should be able to configure >> > their server to report the correct one. >> > >> > --Oliver >> > >> >> >> >> That's alright. >> >> >> >> Thanks for the help. >> >> >> >> >> >> Oliver Hunt-2 wrote: >> >>> >> >>> >> >>> Your host is serving the SVG files with text/plain as the mimetype, >> >>> you'll need to contact your host so that they can setup the server to >> >>> report the correct mimetype. >> >>> >> >>> --Oliver >> >>> >> >>> On 27/09/2007, at 6:19 PM, kizzume wrote: >> >>> >> >>>> >> >>>> >> >>>> Is this something you can tell if you try to look at the file, >> >>>> because I >> >>>> really truly have absolutely no idea what you're talking about. >> >>>> All I know >> >>>> about the kind of server I have is that it holds files. I log in >> >>>> with >> >>>> FireFTP, create directories, and upload files. It's one I pay a >> >>>> yearly fee >> >>>> for. That probably doesn't tell you anything though. >> >>>> >> >>>> The server is not an application server--it just holds files. >> >>>> >> >>>> Here's one I made a copy of that was working perfectly on another >> >>>> server: >> >>>> http://www.infraxes.com/kizzume/images/flag_of_france.svg >> >>>> >> >>>> Here's one I converted with inkscape from a bmp: >> >>>> >> >>>> http://www.infraxes.com/kizzume/images/kizzume-logo.svg >> >>>> >> >>>> And here's a stupid test drawing made in inkscape: >> >>>> >> >>>> http://www.infraxes.com/kizzume/images/drawing.svg >> >>>> >> >>>> >> >>>> >> >>>> Oliver Hunt-2 wrote: >> >>>>> >> >>>>> >> >>>>> First guess: Your server isn't sending the correct mimetype -- you >> >>>>> should make sure it is definitely being sent as image/svg+xml >> >>>>> >> >>>>> --Oliver >> >>>>> >> >>>>> On 26/09/2007, at 5:22 AM, kizzume wrote: >> >>>>> >> >>>>>> >> >>>>>> I can take an svg file from another server that works great when I >> >>>>>> embed it >> >>>>>> into a page, but as soon as I copy that same svg file to my server >> >>>>>> and host >> >>>>>> it there, it won't view as a picture--it just shows it in text >> >>>>>> form >> >>>>>> instead. >> >>>>>> >> >>>>>> Am I doing something wrong, or are there some servers that put >> >>>>>> on a >> >>>>>> strange >> >>>>>> limitation or something? >> >>>>>> -- >> >>>>>> View this message in context: http://www.nabble.com/I-can%27t- >> >>>>>> seem- >> >>>>>> to-host-svg-files...-tf4522017.html#a12899768 >> >>>>>> Sent from the w3.org - www-svg mailing list archive at Nabble.com. >> >>>>>> >> >>>>>> >> >>>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>> >> >>>> -- >> >>>> View this message in context: http://www.nabble.com/I-can%27t-seem- >> >>>> to-host-svg-files...-tf4522017.html#a12933163 >> >>>> Sent from the w3.org - www-svg mailing list archive at Nabble.com. >> >>>> >> >>>> >> >>> >> >>> >> >>> >> >>> >> >> >> >> -- >> >> View this message in context: http://www.nabble.com/I-can%27t-seem- >> >> to-host-svg-files...-tf4522017.html#a12935804 >> >> Sent from the w3.org - www-svg mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/I-can%27t-seem-to-host-svg-files...-tf4522017.html#a12936069 >> Sent from the w3.org - www-svg mailing list archive at Nabble.com. >> >> >> > > > -- > Cheers! > Rick > > > -- View this message in context: http://www.nabble.com/I-can%27t-seem-to-host-svg-files...-tf4522017.html#a12937555 Sent from the w3.org - www-svg mailing list archive at Nabble.com.
Received on Friday, 28 September 2007 10:00:43 UTC