Webhost won't change server config

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Tony Carnell

    Webhost won't change server config

    Hi all,

    A couple of days ago I posted a message to this newsgroup relating to the
    fact that a design I'd worked on for a client wasn't displaying its
    stylesheet in Mozilla browsers.
    I was advised by a couple of other newsgroup members far more knowledgeable
    that I on this subject that I should contact the Web host and ask them to
    alter the way the server was sending the CSS from content type
    "applicatio n/x-pointplus" to "text/css" instead.

    This I duly did but they have come back to me saying:
    "We do not make any changes to config on shared servers. Your site is shared
    with lots of others, and if we make changes this could impact on them".

    Does this sound like a reasonable response? How badly could this alteration
    impact on other websites that share the same server?
    I could tell the client to go for a dedicated server, but that would be
    costly.
    I could also tell the client to change Web hosts, but I feel I need more
    information before doing this, and if it's possible to resolve this matter
    with the current host it would make life a lot easier all round.

    All information / advice will be greatly appreciated.

    Thanks,
    Tony.


  • Harlan Messinger

    #2
    Re: Webhost won't change server config


    "Tony Carnell" <tony@fluvius.c o.uk> wrote in message
    news:KSxec.6800 7$Id.47096@news-binary.blueyond er.co.uk...[color=blue]
    > Hi all,
    >
    > A couple of days ago I posted a message to this newsgroup relating to the
    > fact that a design I'd worked on for a client wasn't displaying its
    > stylesheet in Mozilla browsers.
    > I was advised by a couple of other newsgroup members far more[/color]
    knowledgeable[color=blue]
    > that I on this subject that I should contact the Web host and ask them to
    > alter the way the server was sending the CSS from content type
    > "applicatio n/x-pointplus" to "text/css" instead.
    >
    > This I duly did but they have come back to me saying:
    > "We do not make any changes to config on shared servers. Your site is[/color]
    shared[color=blue]
    > with lots of others, and if we make changes this could impact on them".[/color]

    I'm curious how many web sites require that files with the extension ".css"
    be served as any content type OTHER than "text/css". How did it get to be
    "applicatio n/x-pointplus" in the first place? What IS that content type?

    Comment

    • Harlan Messinger

      #3
      Re: Webhost won't change server config


      "Tony Carnell" <tony@fluvius.c o.uk> wrote in message
      news:KSxec.6800 7$Id.47096@news-binary.blueyond er.co.uk...[color=blue]
      > Hi all,
      >
      > A couple of days ago I posted a message to this newsgroup relating to the
      > fact that a design I'd worked on for a client wasn't displaying its
      > stylesheet in Mozilla browsers.
      > I was advised by a couple of other newsgroup members far more[/color]
      knowledgeable[color=blue]
      > that I on this subject that I should contact the Web host and ask them to
      > alter the way the server was sending the CSS from content type
      > "applicatio n/x-pointplus" to "text/css" instead.
      >
      > This I duly did but they have come back to me saying:
      > "We do not make any changes to config on shared servers. Your site is[/color]
      shared[color=blue]
      > with lots of others, and if we make changes this could impact on them".[/color]

      I'm curious how many web sites require that files with the extension ".css"
      be served as any content type OTHER than "text/css". How did it get to be
      "applicatio n/x-pointplus" in the first place? What IS that content type?

      Comment

      • Neal

        #4
        Re: Webhost won't change server config

        On Mon, 12 Apr 2004 15:39:32 +0100, Tony Carnell <tony@fluvius.c o.uk>
        wrote:
        [color=blue]
        > Hi all,
        >
        > A couple of days ago I posted a message to this newsgroup relating to the
        > fact that a design I'd worked on for a client wasn't displaying its
        > stylesheet in Mozilla browsers.
        > I was advised by a couple of other newsgroup members far more
        > knowledgeable
        > that I on this subject that I should contact the Web host and ask them to
        > alter the way the server was sending the CSS from content type
        > "applicatio n/x-pointplus" to "text/css" instead.[/color]

        Apache server? If so, simply use a .htaccess file.
        [color=blue]
        > This I duly did but they have come back to me saying:
        > "We do not make any changes to config on shared servers. Your site is
        > shared
        > with lots of others, and if we make changes this could impact on them".[/color]

        Unreasonable. By far text/css is more universally appropriate.

        Explain to them again, noting that your client *really needs to* serve
        ..css as text/css. If still no help, dump them in favor of a host using
        Apache, where you can set an .htaccess and forget about it.

        Comment

        • Neal

          #5
          Re: Webhost won't change server config

          On Mon, 12 Apr 2004 15:39:32 +0100, Tony Carnell <tony@fluvius.c o.uk>
          wrote:
          [color=blue]
          > Hi all,
          >
          > A couple of days ago I posted a message to this newsgroup relating to the
          > fact that a design I'd worked on for a client wasn't displaying its
          > stylesheet in Mozilla browsers.
          > I was advised by a couple of other newsgroup members far more
          > knowledgeable
          > that I on this subject that I should contact the Web host and ask them to
          > alter the way the server was sending the CSS from content type
          > "applicatio n/x-pointplus" to "text/css" instead.[/color]

          Apache server? If so, simply use a .htaccess file.
          [color=blue]
          > This I duly did but they have come back to me saying:
          > "We do not make any changes to config on shared servers. Your site is
          > shared
          > with lots of others, and if we make changes this could impact on them".[/color]

          Unreasonable. By far text/css is more universally appropriate.

          Explain to them again, noting that your client *really needs to* serve
          ..css as text/css. If still no help, dump them in favor of a host using
          Apache, where you can set an .htaccess and forget about it.

          Comment

          • Andrew Urquhart

            #6
            Re: Webhost won't change server config

            Harlan Messinger wrote:[color=blue]
            > I'm curious how many web sites require that files with the extension
            > ".css" be served as any content type OTHER than "text/css". How did
            > it get to be "applicatio n/x-pointplus" in the first place? What IS
            > that content type?[/color]

            It's quite common apparently:



            "The file type .css is not mapped to cascading style sheets in the
            default mime types included with Enterprise Server"
            --
            Andrew Urquhart
            - FAQ: www.css.nu/faq/ciwas-aFAQ.html
            - Archive: www.tinyurl.com/ysjbm
            - Contact: www.andrewu.co.uk/contact/
            - Employ me: Front/middle tier ASP developer with WAI & web standards


            Comment

            • Andrew Urquhart

              #7
              Re: Webhost won't change server config

              Harlan Messinger wrote:[color=blue]
              > I'm curious how many web sites require that files with the extension
              > ".css" be served as any content type OTHER than "text/css". How did
              > it get to be "applicatio n/x-pointplus" in the first place? What IS
              > that content type?[/color]

              It's quite common apparently:



              "The file type .css is not mapped to cascading style sheets in the
              default mime types included with Enterprise Server"
              --
              Andrew Urquhart
              - FAQ: www.css.nu/faq/ciwas-aFAQ.html
              - Archive: www.tinyurl.com/ysjbm
              - Contact: www.andrewu.co.uk/contact/
              - Employ me: Front/middle tier ASP developer with WAI & web standards


              Comment

              • Spartanicus

                #8
                Re: Webhost won't change server config

                "Tony Carnell" <tony@fluvius.c o.uk> wrote:
                [color=blue]
                >"We do not make any changes to config on shared servers. Your site is shared
                >with lots of others, and if we make changes this could impact on them".
                >
                >Does this sound like a reasonable response?[/color]

                No, grossly incompetent bunch of idiots.

                Change host.

                --
                Spartanicus

                Comment

                • Spartanicus

                  #9
                  Re: Webhost won't change server config

                  "Tony Carnell" <tony@fluvius.c o.uk> wrote:
                  [color=blue]
                  >"We do not make any changes to config on shared servers. Your site is shared
                  >with lots of others, and if we make changes this could impact on them".
                  >
                  >Does this sound like a reasonable response?[/color]

                  No, grossly incompetent bunch of idiots.

                  Change host.

                  --
                  Spartanicus

                  Comment

                  • Alan J. Flavell

                    #10
                    Re: Webhost won't change server config

                    On Mon, 12 Apr 2004, Tony Carnell wrote:
                    [color=blue]
                    > that I on this subject that I should contact the Web host and ask
                    > them to alter the way the server was sending the CSS from content
                    > type "applicatio n/x-pointplus" to "text/css" instead.
                    >
                    > This I duly did but they have come back to me saying:
                    > "We do not make any changes to config on shared servers. Your site is shared
                    > with lots of others, and if we make changes this could impact on them".
                    >
                    > Does this sound like a reasonable response?[/color]

                    As a general principle - yes, naturally they should not make
                    arbitrary changes for one customer when it's going to have an
                    impact on their other customers.

                    In this particular case - emphatically no. The x- prefix in that
                    content-type shows that it's "experiment al": this problem was noticed
                    and solved in 1996, to my knowledge, on servers where it was being
                    spotted, and there's no way that a content-type had any privileged
                    rights if it remained "experiment al" for that length of time.
                    [color=blue]
                    > How badly could this alteration
                    > impact on other websites that share the same server?[/color]

                    I'd suggest a read of


                    Personally I couldn't be bothered to research this for myself again
                    now, as the answer seems clear enough to me.
                    [color=blue]
                    > I could tell the client to go for a dedicated server, but that would be
                    > costly.[/color]

                    If they don't give an individual content provider the ability to
                    control their own content-type headers, SHOUT LOUDLY: this is
                    something that they NEED for doing their job properly.

                    (Apologies to Mark Nottingham for plagiarising his theme ;-)

                    In Apache this would mean they'd need to enable the relevant feature
                    in the .htaccess file, and the content provider would then supply an
                    AddType directive in their (highest-level) .htaccess file. Other
                    servers, of course, may use different configuration mechanisms.
                    [color=blue]
                    > All information / advice will be greatly appreciated.[/color]

                    I think you've been given the standard knee-jerk level 1 user support
                    response. I'd say go back to them and say their answer is
                    unsatisfactory, and ask to speak to the next level of technical
                    support. Somebody there needs to recognise that they're supporting
                    some way-obsolete experimental-only content type, to the detriment of
                    one which -has- been properly registered with the authorities (IANA).

                    good luck

                    Comment

                    • Alan J. Flavell

                      #11
                      Re: Webhost won't change server config

                      On Mon, 12 Apr 2004, Tony Carnell wrote:
                      [color=blue]
                      > that I on this subject that I should contact the Web host and ask
                      > them to alter the way the server was sending the CSS from content
                      > type "applicatio n/x-pointplus" to "text/css" instead.
                      >
                      > This I duly did but they have come back to me saying:
                      > "We do not make any changes to config on shared servers. Your site is shared
                      > with lots of others, and if we make changes this could impact on them".
                      >
                      > Does this sound like a reasonable response?[/color]

                      As a general principle - yes, naturally they should not make
                      arbitrary changes for one customer when it's going to have an
                      impact on their other customers.

                      In this particular case - emphatically no. The x- prefix in that
                      content-type shows that it's "experiment al": this problem was noticed
                      and solved in 1996, to my knowledge, on servers where it was being
                      spotted, and there's no way that a content-type had any privileged
                      rights if it remained "experiment al" for that length of time.
                      [color=blue]
                      > How badly could this alteration
                      > impact on other websites that share the same server?[/color]

                      I'd suggest a read of


                      Personally I couldn't be bothered to research this for myself again
                      now, as the answer seems clear enough to me.
                      [color=blue]
                      > I could tell the client to go for a dedicated server, but that would be
                      > costly.[/color]

                      If they don't give an individual content provider the ability to
                      control their own content-type headers, SHOUT LOUDLY: this is
                      something that they NEED for doing their job properly.

                      (Apologies to Mark Nottingham for plagiarising his theme ;-)

                      In Apache this would mean they'd need to enable the relevant feature
                      in the .htaccess file, and the content provider would then supply an
                      AddType directive in their (highest-level) .htaccess file. Other
                      servers, of course, may use different configuration mechanisms.
                      [color=blue]
                      > All information / advice will be greatly appreciated.[/color]

                      I think you've been given the standard knee-jerk level 1 user support
                      response. I'd say go back to them and say their answer is
                      unsatisfactory, and ask to speak to the next level of technical
                      support. Somebody there needs to recognise that they're supporting
                      some way-obsolete experimental-only content type, to the detriment of
                      one which -has- been properly registered with the authorities (IANA).

                      good luck

                      Comment

                      • Harlan Messinger

                        #12
                        Re: Webhost won't change server config


                        "Alan J. Flavell" <flavell@ph.gla .ac.uk> wrote in message
                        news:Pine.LNX.4 .53.04041215491 40.14745@ppepc5 6.ph.gla.ac.uk. ..[color=blue]
                        > On Mon, 12 Apr 2004, Tony Carnell wrote:
                        >[color=green]
                        > > that I on this subject that I should contact the Web host and ask
                        > > them to alter the way the server was sending the CSS from content
                        > > type "applicatio n/x-pointplus" to "text/css" instead.
                        > >
                        > > This I duly did but they have come back to me saying:
                        > > "We do not make any changes to config on shared servers. Your site is[/color][/color]
                        shared[color=blue][color=green]
                        > > with lots of others, and if we make changes this could impact on them".
                        > >
                        > > Does this sound like a reasonable response?[/color]
                        >
                        > As a general principle - yes, naturally they should not make
                        > arbitrary changes for one customer when it's going to have an
                        > impact on their other customers.
                        >
                        > In this particular case - emphatically no. The x- prefix in that
                        > content-type shows that it's "experiment al": this problem was noticed
                        > and solved in 1996, to my knowledge, on servers where it was being
                        > spotted, and there's no way that a content-type had any privileged
                        > rights if it remained "experiment al" for that length of time.[/color]

                        I would think that the real issue is that it's the *wrong* content type for
                        serving CSS files, rather than because it's an *experimental* one.
                        Otherwise, what do you have to say about the fact that the default enctype
                        for HTML forms remains "applicatio n/x-www-form-urlencoded"?


                        Comment

                        • Harlan Messinger

                          #13
                          Re: Webhost won't change server config


                          "Alan J. Flavell" <flavell@ph.gla .ac.uk> wrote in message
                          news:Pine.LNX.4 .53.04041215491 40.14745@ppepc5 6.ph.gla.ac.uk. ..[color=blue]
                          > On Mon, 12 Apr 2004, Tony Carnell wrote:
                          >[color=green]
                          > > that I on this subject that I should contact the Web host and ask
                          > > them to alter the way the server was sending the CSS from content
                          > > type "applicatio n/x-pointplus" to "text/css" instead.
                          > >
                          > > This I duly did but they have come back to me saying:
                          > > "We do not make any changes to config on shared servers. Your site is[/color][/color]
                          shared[color=blue][color=green]
                          > > with lots of others, and if we make changes this could impact on them".
                          > >
                          > > Does this sound like a reasonable response?[/color]
                          >
                          > As a general principle - yes, naturally they should not make
                          > arbitrary changes for one customer when it's going to have an
                          > impact on their other customers.
                          >
                          > In this particular case - emphatically no. The x- prefix in that
                          > content-type shows that it's "experiment al": this problem was noticed
                          > and solved in 1996, to my knowledge, on servers where it was being
                          > spotted, and there's no way that a content-type had any privileged
                          > rights if it remained "experiment al" for that length of time.[/color]

                          I would think that the real issue is that it's the *wrong* content type for
                          serving CSS files, rather than because it's an *experimental* one.
                          Otherwise, what do you have to say about the fact that the default enctype
                          for HTML forms remains "applicatio n/x-www-form-urlencoded"?


                          Comment

                          • Tony Carnell

                            #14
                            Re: Webhost won't change server config

                            Thanks for all your help and advice.

                            I'll go back to the Web host now armed with this new information. :-)

                            Regards,
                            Tony.


                            Comment

                            • Tony Carnell

                              #15
                              Re: Webhost won't change server config

                              Thanks for all your help and advice.

                              I'll go back to the Web host now armed with this new information. :-)

                              Regards,
                              Tony.


                              Comment

                              Working...