claire rand
01-07-2005, 02:27 PM
Ok now i've created an xml file.. and the related xsl formatting file, and even a css file handling the actual colours etc.
problem.. the above works fine locally, and even works via apache on my own local server.
problem #1 i can't upload xml & xsl & css files to one of my webspaces, it has to be a htm file. now so far i've got round this for css files by calling them 'htm' files, this doesn't seem to break anything. but the xml file renders differently if called an 'htm' file so thats out. Does this imply the browser is looking at teh filename to determine how the file should look instead of the actual file itself?
Is there a way round this and to enable me to call the files *anything* and still have them work (assuming they call each other via the correct names ect). thus i can upload them as *.htm files and still have them work?
problem #2 my other webspace lets me upload the files, even shows them as 'text/xml' & 'text/xsl' but it renders them as plain old htm files still..
any way round this?
there has got to be a way for a file to say 'I'm a xxx file, treat me as such' and cut the server out of the loop so to speak.
My linux box generally identifies files fine, regardless of the filename or extension, i know windows uses the extension but i thought the web worked on the unix mime-type model?
problem.. the above works fine locally, and even works via apache on my own local server.
problem #1 i can't upload xml & xsl & css files to one of my webspaces, it has to be a htm file. now so far i've got round this for css files by calling them 'htm' files, this doesn't seem to break anything. but the xml file renders differently if called an 'htm' file so thats out. Does this imply the browser is looking at teh filename to determine how the file should look instead of the actual file itself?
Is there a way round this and to enable me to call the files *anything* and still have them work (assuming they call each other via the correct names ect). thus i can upload them as *.htm files and still have them work?
problem #2 my other webspace lets me upload the files, even shows them as 'text/xml' & 'text/xsl' but it renders them as plain old htm files still..
any way round this?
there has got to be a way for a file to say 'I'm a xxx file, treat me as such' and cut the server out of the loop so to speak.
My linux box generally identifies files fine, regardless of the filename or extension, i know windows uses the extension but i thought the web worked on the unix mime-type model?