Skip navigation
harvey waxman
harvey waxman
Currently Being Moderated

Grizzly bad request error

Jul 29, 2012 4:04 PM

Can anyone tell me what the Grizzly Bad Request error means?  It's on all pages so it could be from the css file but could it be something else, like the switch to a new server?

 

Thanks.

722 Views   8 Replies   Latest reply: harvey waxman, Jul 30, 2012 5:18 PM
 
Replies
  • Ken Binney
    Currently Being Moderated
    1. Ken Binney,
    Jul 29, 2012 4:52 PM   in reply to harvey waxman
    Report

    Not appearing now

    New York 7:53 EDT

     
    |
    Mark as:
  • harvey waxman
    Currently Being Moderated
    2. harvey waxman,
    Jul 29, 2012 4:55 PM   in reply to Ken Binney
    Report

    I've since discovered it appears only in Safari on my Mac in the last day or so .  A real puzzler.  Thanks

     
    |
    Mark as:
  • mytaxsite.co.uk
    Currently Being Moderated
    3. mytaxsite.co.uk,
    Jul 29, 2012 6:53 PM   in reply to harvey waxman
    Report

    harvey waxman wrote:

     

    I've since discovered it appears only in Safari on my Mac in the last day or so .  A real puzzler.  Thanks

     

    In that case your first port of call should be validation.  Try this link for css errors:

     

    <http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fdinghydo gs.com%2F&profile=none&usermedium=all&warning=1&vextwarning=&lang=en>

     

    and this link for HTML errors:

     

    <http://validator.w3.org/check?uri=http%3A%2F%2Fdinghydogs.com%2F&chars et=%28detect+automatically%29&doctype=Inline&group=0&ss=1&st=1&outline =1&No200=1&verbose=1>

     

    Good luck and post back.

     
    |
    Mark as:
  • harvey waxman
    Currently Being Moderated
    4. harvey waxman,
    Jul 30, 2012 5:59 AM   in reply to mytaxsite.co.uk
    Report

    Thanks for those suggestions.  I made the corrections to the css style sheet with no improvement.  There were several html issues as well and I made some of those too but remember, the issue is only on Safari's rendering of the two sites in question so I suspect that it is an issue unique to this version of Safari.  The error doesn't appear on versions after 5.0.6

     
    |
    Mark as:
  • mytaxsite.co.uk
    Currently Being Moderated
    5. mytaxsite.co.uk,
    Jul 30, 2012 4:37 PM   in reply to harvey waxman
    Report

    harvey waxman wrote:

     

    Thanks for those suggestions.  I made the corrections to the css style sheet with no improvement.  There were several html issues as well and I made some of those too but remember, the issue is only on Safari's rendering of the two sites in question so I suspect that it is an issue unique to this version of Safari.  The error doesn't appear on versions after 5.0.6

     

    OK let's first try to clear all HTML errors and/or warnings:

     

    1:) First you have defined id="BOTTOMNAV" at various places on your page:

     

    Lines: 153, 161, 178   (search for others just in case I have missed something)

     

    You can have onl;y one ID of that name on a page and so you need to rename the other two IDs.  IDs are quite different from classes;  Classes can be defined as many times as you want but not IDs.

     

    So correct this and post back to see if anything has changed.

     

    We'll deal with other errors one by one later but some errors and/or warning will disappeasr when majot corrections are done first.

     

    Please post back when you can.

     
    |
    Mark as:
  • harvey waxman
    Currently Being Moderated
    6. harvey waxman,
    Jul 30, 2012 5:00 PM   in reply to mytaxsite.co.uk
    Report

    I am aware that there are some css violations.  I have another file with the same violations that does not exhibit the error I mention.  Since apparently no one can see the error but I with my version of Safari I don't believe that is the issue.

     

    I will spend some time reviewing my errors and I will correct them but I know that they are unrelated to the phenomenon.  I opened another version of the index file and viewed it in Safari and the "bad request"  wasn't there.  I searched this file and found several identical ID's as in the defective file. I then viewed that defective file and the "bad request" message was GONE!

     

    I then went online and sure enough the messages were gone from all pages in both previously affected files as well. The error has vanished.

     

    I had moved the .plist files from Safari to the trash and restarted it.  The errors remained.  I repaired permissions, tried to download a new copy of Safari but couldn't, so I moved the trashed .plist files back.

     

    Maybe that had something to do with this crazy puzzle but I'm afraid I'll never know.  I will fix the ID's though and learn more about proper CSS syntax.

     

    Thanks for very kind attention and suggestions.

     
    |
    Mark as:
  • mytaxsite.co.uk
    Currently Being Moderated
    7. mytaxsite.co.uk,
    Jul 30, 2012 5:09 PM   in reply to harvey waxman
    Report

    Your CSS is perfect now.  There are no errors according to the validation engine.  It is the HTML errors that needs to be corrected.  Some of them are minor but others are quite serious and IMHO should be corrected. 

     

    I am using Firefox and IE9 and I don't see the errors you were talking about but it is up top you whether to correct HTML errors or not.  Personally I would just to clear my conscious!!

     

    Good luck.

     
    |
    Mark as:
  • harvey waxman
    Currently Being Moderated
    8. harvey waxman,
    Jul 30, 2012 5:18 PM   in reply to mytaxsite.co.uk
    Report

    I fully agree.  I've got some reading to do.  Many thanks for your help.

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points