IIS6 - W3C Compliant - WebHelp Explosions

Here's an interesting issue that I would like to hear everyone's opinions regarding. I received an e-mail from my client's networking guy the other day stating that he was getting a random error every now and again when clicking on multiple topics in the WebHelp I created. I was confused BEYOND BELIEF! I had never run into a problem with this before, and I've created tons of help systems in the past. I would be interested to hear what you all think I could have done differently to prevent this from occuring. (Don't check the W3C Compliant checkbox, etc) It's a very interesting use case....and hopefully this helps someone else who may run into such a situation.
He sent me this e-mail this morning saying that it's fixed...
Error Message
The issue with the error message showing after a number of page hits has been fixed.  The issue is with the headers on each file.  They are not proper for IIS6 due to a major flaw in IIS6.  I verified this without creating a virtual directory which means that these pages are served up as pure html and bypass my security.
The solution is to delete the first 5 lines of every file and replace with the following.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
The lines being removed are:
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!-- saved from url=(0014)about:internet -->
<html xmlns="http://www.w3.org/1999/xhtml">
There is an article at http://w3.org/brief/MTE2 that explains this issue.  Basically, IIS is downloading the instructions on how to handle an XML formatted document from the w3 site every time a page is requested.  Since this document never changes, these unnecessary downloads are being treated as a Denial Of Service attack and our server’s IP eventually gets blocked.  The header that we are now using is more appropriate anyway.

Hello Harvey -
Testing your initial post wasn't a waste of time...in fact I
learned a VERY IMPORTANT LESSON about RH, IE, Firefox, Opera and
image/hyperlink screen tips.
I learned that IE6 "screen tip on hover" reads the RH "Image
screen tip" entry but FF and Opera read the RH "Hyperlink screen
tip" entry.
THUS: to make IE and FF/Opera screen tips "appear" the same,
one must enter the SAME screen tip into BOTH the Image Screen Tip
text box and the Hyperlink Screen Tip text box!
(Now, how long will it take me to check 3,000 images and
hyperlinks in my current project?)
Regards,
GEWB

Similar Messages

  • Links from images broken in "W3C Compliant"

    I raised a false alarm, for which I apologize.
    There is one issue that affects IE when WebHelp is generated
    with W3C Compliant topics. Please see a new post about that.
    There are some code differences, but they do not break links
    to a popup or jump to another topic in IE 6, IE 7, or Firefox
    2.0.0.13 (released yesterday).
    Again, if anyone wasted time trying to verify broken links, I
    am truly sorry.
    Harvey

    Hello Harvey -
    Testing your initial post wasn't a waste of time...in fact I
    learned a VERY IMPORTANT LESSON about RH, IE, Firefox, Opera and
    image/hyperlink screen tips.
    I learned that IE6 "screen tip on hover" reads the RH "Image
    screen tip" entry but FF and Opera read the RH "Hyperlink screen
    tip" entry.
    THUS: to make IE and FF/Opera screen tips "appear" the same,
    one must enter the SAME screen tip into BOTH the Image Screen Tip
    text box and the Hyperlink Screen Tip text box!
    (Now, how long will it take me to check 3,000 images and
    hyperlinks in my current project?)
    Regards,
    GEWB

  • My muse site does not pass the W3C compliant test. Why?

    I ran the W3C compliant program against my home page generated HTML from Muse.  It complained about missing arguments and the use of some obsolete statements.  Is anyone else having this sort of problem?

    Do you have any custom HTML added to your site through Object -> Insert HTML option or HTML for <head> in Page Properties that contains broken HTML causing the problem? A site URL would help in identifying the issue.
    Thanks,
    Vinayak

  • How to make a div clickable and still be w3c compliant

    Can someone help me to make a div clickable so it is still w3c compliant?This is my current div and it seems to work, but when I check for compliance I get "unexpected end tag (a not expected). ???
    <div id="pic-wrapper">
    <a href="../index.htm"><div id="pic"></div></a></div>
    Appreciate any help. Thank you.

    This is something I've never needed to do mysefl, but it ought to work ok.  And do not remove your standard a tag with its link currenlty inside the div so Search Engines will be able to spider the link and users without javascript will be able to reach it as well.  I've added the code in orange:
    <div id="pic-wrapper" onclick="location.href='http://www.yourwebsite.com/index.htm';" style="cursor: pointer;">
    <a href="../index.htm"><div id="pic"></div></a></div>
    I just guessed your link was to the homepage, so that is what I replicated in orange, but of course you would be sure to change the link to the correct absolute address.
    Let us know how this works for you.
    E. Michael Brandt
    www.divahtml.com
    www.divahtml.com/products/scripts_dreamweaver_extensions.php
    Standards-compliant scripts and Dreamweaver Extensions
    www.valleywebdesigns.com/vwd_Vdw.asp
    JustSo PictureWindow
    JustSo PhotoAlbum, et alia

  • Inserting flash w3c compliant

    Hi guys
    I’m inserting a flash banner into my page. If I do it
    through dreamweaver it works fine on all browsers although it is
    not w3c compliant due to the fact that it is embedded. I have got
    it w3c compliant (no embedded) although firefox does not display it
    (over 25% of users) is there a work around this?
    Cheers guys

    For xhtml valid code you'd need to use the Flash Satay method
    http://www.alistapart.com/articles/flashsatay/
    Although that has few issues itself, covered in the article.
    Hope this helps

  • 508 & W3C compliance

    If you check to generate Section 508 Compliant Output AND W3C
    Compliant Topics, exactly WHAT CHANGES in the help files? What is
    different? improved? whatever?

    Thank you Jinx1 for posting this message. While I acknowledge
    the position of senior members in the availability of their time
    and that they are doing a great job getting to posting, it may be
    difficult for them to understand that the demand for answers to
    deficiencies in compliance can be as intimidating as undergoing a
    U.S. Congressional hearing depending upon how sensible the folks
    are conducting the compliance checks. My perspective is that there
    is value in having a centralized posting of this information. Just
    consider the amount of research time and money each government
    employee or contractor spends in finding these very same answers
    for themselves.
    That said for your immediate future, it may help for you to
    change your perspective from the source file differences to the
    output differences. Take a look at how testing for compliance will
    be done by your governing agency. We just completed a W3C Level
    1,2,3 compliance check of RoboHelp 6 webhelp having both the
    settings you mentioned. There was a third-party tool used to verify
    Accessibility. There are freeware versions of tools available for
    accessibilty testing. It will give you the specific differences in
    the htm files and identify the rules broken.
    With our RH6 results, even with 508 compliance and W3C
    checked, there were still elements flagged like the use of frames,
    no titles for those frames, and the lack of a NOFRAMES alternative.
    Also there was an applet used without any titling or an alternative
    means to get it. (I'm not sure what this applet does.) The same
    frame related elements are flagged in a comparison with a NON-508
    compliant default-skin version. The main difference between the two
    seems to be the use of non-titled images (mainly the books and page
    graphics that make up the TOC), also the navigation buttons at the
    top do not have alt or longdesc tags.
    With either output, it may be less stressful to find out if
    compliance really is YOUR problem to deal with. Was there a product
    selection process and who was involved? Can they help? There may be
    creative alternatives that the governing agency may come up with or
    exceptions made on a case-by-case basis.
    Good luck!

  • Re : Highlight Search rsults in RoboHelp 7 (webHelp)

    Hello there,
    How are you ? I am a newbie at using Robohelp. Our company
    just purchsed Robohelp licenses and I was trying to pickup this
    tool. I could create the html help file with TOC and Index. Search
    works great but what's baffling me is that the Search results don't
    highlight the search word.
    I tried to Google it but it brought that you had to right
    some JS to highlight and add it to ALL help pages onload(). But ,
    it said that V7 had these feature out of the box...I tried looking
    but couldn't find it .
    Can someone please help me with this. Thanks in advance.
    - Sam

    Hello Rick,
    How are you ? Thaks for your quick response. Appreciate it. I
    am obviously missing something!! Yes, I am using WebHelp Single
    Source Primary layout output.
    However, as you suggested when I click on View I don't see
    Pods .
    Moreover, I double clicked on the WebHelp layout (In project
    Tab, Under Dependencies Folder icon)
    Click the Next > button at the bottom of the dialog
    But that didn't bring me the option for Search
    highlighting!!!! Instead, I am seeing option to make output 508 /
    W3C compliant. I am using Robohelp 7.0 Build 145 . Also, I am
    currently on trial version , yet, to receive the license keys from
    Sales guy. You think that could be it ? I wanted to attach the
    snapshot of what I am seeing( didn't find option in forum) where I
    am suppose to see Search highlight option
    Thanks again,
    Sam

  • Merging Webhelp Projects

    When merging two webhelp projects (in version 7), the
    subtopic is opening in a new window and the indexes are not merged.
    I looked it up in the help and there is a note at the bottom that
    says: "Merging WebHelp/FlashHelp projects with a pure HTML master
    project or Section 508 compliant WebHelp/FlashHelp causes the
    subprojects to be available only from the TOC. Subprojects will
    appear as a book in the TOC. Sub-project TOC books will open the
    subproject in a new browser window." That is exactly what I don't
    want to happen! I was able to do it in other versions easily. What
    other options do I have? All the options on the Navigation Pane
    Preferred Format tab includes PureHTML. Any advice will be
    great!

    There's a complete tutorial on my site.

  • W3C Markup Validation

    Can someone please help me understand what it is I need to
    fix in order for my site to be W3C compliant?
    W3C My site is
    my site
    Thank you,
    Falofal

    Falofal posted in macromedia.dreamweaver
    > Can someone please help me understand what it is I need
    to fix in
    > order for my site to be W3C compliant?
    http://validator.w3.org/ My
    > site is
    http://www.sourcelake.ca/test8/
    I see you've produced valid XHTML (why XHTML?). You'll also
    want to use
    their CSS validator at
    http://jigsaw.w3.org/css-validator/
    Change:
    font: "Times New Roman", Times, serif;
    to:
    font-family: "Times New Roman", Times, serif;
    Change:
    ssssbackground-color: #333;
    to:
    background-color: #333;
    I don't know what to make of the errors in ul.MenuBarVertical
    iframe in
    SpryMenuBarVertical.css. They seem to be an IE hack without
    actually
    targeting IE in the CSS. You might be able to ignore them.
    Mark A. Boyd
    Keep-On-Learnin' :)

  • W3C validation... Stray end tag img

    How to fix these w3c html errors?
    Bad value X-UA-Compatible for attribute http-equiv on element meta.
    <meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=IE8"/>
    Stray end tag img.
    …" src="edgeanimate_assets/test/images/test.png"></img> </div>
    Thanks

    Hey, IronADDT-
    I was able to reproduce this bug and just filed it to be fixed in the next release.  In the meantime, if you're required to be W3C compliant, the only way you can get around it is to hand-edit your HTML file after you've published.
    Thanks,
    -Elaine

  • FF4 is starting to remind me of IE. W3C content variations and even worse, PDF failures.

    FF4 is not displaying content the same as other modern browsers, including the previous version. There appears to be padding or margin bugs that effect W3C compliant web development.
    Even more irritating, PDF documents can no longer be viewed through the browser. I am running the latest non beta version of FF4, the latest version of adobe reader, and you always get a blank page. This is such a horrible oversight of Mozilla.
    FF is SUPPOSE to be the productive alternative of IE, and frankly, it's becoming IE like. Don't make me go to chrome.

    Give <div class="container"> the same blue background color as your right side bar.
    You'll notice in IE some of the spacing for the rest of your page is slightly larger than in Firefox (browsers do that a lot if you aren't very, very specific about sizes). Because of that, your side bar isn't long enough to fill in the space on that side and the background color of the "container" <div> shows through.

  • W3C compliance of EP

    We have a client that is expressing interest in portals as a consumer-facing solution, but they want to ensure that portals is W3C compliant up to priority 2.
    Does anyone have any reference to SAP documentation that supports EP as conforming to W3C standards?
    Any help with this would be much appreciated.
    Thanks and regards,
    Eugene

    Hi Eugene,
    Check out this <a href="http://www.x-istech.com/html/intranet.aspx">link</a>. It will be of some help.
    Regards,
    Pooja.

  • Can't Open an Excel File

    I just started trying out the trial version of RoboHelp and
    I'm using WebHelp to create my help file.
    In one of my topics I have a word document that lists on call
    information. I then have a link from a name
    on that list to open up an Excel spreadsheet (I highlighted
    the text, then Insert Hyperlink).
    I then: Save, Generate Primary Layout, then View Results.
    That opens up the htm file (helpfile.htm).
    My spreadsheet link is there (its at least underlined), but
    you can't click it.
    Assuming I'm explaining all of this good enough
    any suggestions on what I'm screwing up?
    If you need any more info, just let me know.
    Thanks
    Doug

    Ok,
    First Rick.
    When I get to the box where the choice of skins are, right
    above it, the choices are:
    Section 508 Compliant Output
    W3C Compliant Topics
    I double checked RoboHelps Help...and it says Robohelp for
    Word 6, Build 99.
    Colum...
    Here's what I did (I 'thought', I'd start off simple, lol)...
    1. Start Robo.
    2. Select New Project.
    3. The left panel contains all of the folders (I think its
    called Explorer).
    The right panel is the default Helpfile word document that
    contains the 'welcome' message.
    4. I added my spreadsheet to the Baggage folder.
    5. Back at the word document, I just added a simple word
    'excel'.
    6. Then I highlighted 'excel', Insert->Hyperlink...and
    pointed it to my excel spreadsheet.
    7. Saved it.
    8. Generated it.
    Everything opens up fine in IE. Excel is highlighted blue and
    underlined. But its not clickable.
    Doug

  • Hotspots not working as expected in Safari and Internet Explorer

    first of all, I am using the double <object> tag with conditional comments to hide the inner <object> tag from IE, to embed a QTVR in a web page (as recommended at A List Apart, see http://www.alistapart.com/articles/byebyeembed for details). I am not using the <object><embed> method any longer since <embed> is not standards-compliant.
    second, see this URI
    http://www.30fps.com/html/aboveCristallinaVREn.html
    and/or check out this code:
    ============
    <object classid="clsid:02BF25D5-8C17-4B23-BC80-D3488ABDDC6B" codebase="http://www.apple.com/qtactivex/qtplugin.cab"
    width="480" height="302">
    <param name="src" value="../mov/aboveCristallina02VREn.mov">
    <param name="controller" value="false">
    <param name="align" value="middle">
    <param name="bgcolor" value="#FFFFFF">
    <param name="hotspot88" value="<../html/cristallinaVREn.html> T<_self>">
    <!--[if !IE]>-->
    <object type="video/quicktime" data="../mov/aboveCristallina02VREn.mov"
    width="480" height="302">
    <param name="controller" value="false">
    <param name="align" value="middle">
    <param name="bgcolor" value="#FFFFFF">
    <param name="hotspot88" value="<../html/cristallinaVREn.html> T<_self>">
    </object>
    <!--<![endif]-->
    </object>
    ============
    this is the code I am currently testing and having issues with, for an embedded QTVR movie with blob hotspots. To see the hotspot in the VR, click the target icon at the right of the controller bar then turn around about 180 degrees.
    1) in IE for PC (tested in v5.5 and v6.0), clicked hotspots invariably open in a new window and I cannot figure out any way of forcing them to load in the same window, even using the following code (greatly abbreviated here, of course):
    <object>
    <param name="hotspotXX" value="target.html">
    <param name="targetXX" value="_self">
    </object>
    or
    <object>
    <param name="hotspotXX" value="<target.html> T<_self>">
    </object>
    2) Safari 3.0.4, the hotspots don't work at all. I can only successfully target a URL with a hotspot, when I use <embed> but as noted above, <embed> is not a W3C-compliant tag and I don't wish to use it any longer.
    Naturally, I tried an extensive Google/Apple mail list search already and can't turn up any viable solutions to either.
    TIA for your help...
    Message was edited by: r€nato

    The tag should read "myself" (no quotes) not "_self".
    http://www.apple.com/quicktime/tutorials/embed2.html
    For cross OS browser compatibility (and no "embed" tag code) you should consider using javascript:
    http://developer.apple.com/internet/ieembedprep.html
    With all of my skills I could not get your "hotspot" to open a new html page:
    http://www.30fps.com/mov/aboveCristallina02VREn.mov

  • Hidden field value init. by a var in Netscape && MSIE ...

              Hi there,
              I have a hidden field specified this way :
              <input type = "hidden" name = <%=myName%> value = "<%=myValue%>">
              Suppose that myValue is 'Ionut RUSUBOCA'
              If I run this with Netscape 4.75 it works just fine.
              If I run this with Microsoft IE 5.50.4522.1800 I get an error that points to the
              way the hidden field value is specified.
              If I change ...... value = "<%=myValue%>" ..... to .... value = <%=myValue%>
              ... ( that is, if I remove the double quotes ) then MSIE is Ok but ... instead
              of 'Ionut RUSUBOCA' I only get 'Ionut'.
              Could you, please, help me make MSIE see the correct value that is 'Ionut RUSUBOCA'
              ? ( like Netscape )
              Which browser are not W3C compliant in this matter ?
              Thank you,
              rivisa
              

              Thanks for the reply.
              Well, I quoted everything and still does not work with MSIE.
              Indeed, when I quote value="<%=myValue%>", I get in MSIE value = "Ionut RUSUBOCA"
              but it does not make any difference : it breaks.
              If I take out the quotes ( value = <%=myValue%> ) then the source is viewed as
              value = Ionut RUSUBOCA and when the form
              gets submitted I only get 'Ionut' as value.
              This is weird, so to speak.
              Can you reproduce this thing in your system ?
              Thanks,
              rivisa
              "Cameron Purdy" <[email protected]> wrote:
              >> <input type = "hidden" name = <%=myName%> value = "<%=myValue%>">
              >
              >All attributes should be quoted.
              >
              ><input type="hidden" name="<%=myName%>" value="<%=myValue%>">
              >
              >Look at the result by choosing "View Source" from the MSIE context menu.
              >
              >Peace,
              >
              >--
              >Cameron Purdy
              >Tangosol, Inc.
              >http://www.tangosol.com
              >+1.617.623.5782
              >WebLogic Consulting Available
              >
              >
              >"_rivisa_" <[email protected]> wrote in message
              >news:[email protected]...
              >>
              >>
              >> Hi there,
              >>
              >> I have a hidden field specified this way :
              >>
              >> <input type = "hidden" name = <%=myName%> value = "<%=myValue%>">
              >>
              >> Suppose that myValue is 'Ionut RUSUBOCA'
              >>
              >> If I run this with Netscape 4.75 it works just fine.
              >>
              >> If I run this with Microsoft IE 5.50.4522.1800 I get an error that
              >points
              >to the
              >> way the hidden field value is specified.
              >>
              >> If I change ...... value = "<%=myValue%>" ..... to .... value =
              ><%=myValue%>
              >> ... ( that is, if I remove the double quotes ) then MSIE is Ok but
              >...
              >instead
              >> of 'Ionut RUSUBOCA' I only get 'Ionut'.
              >>
              >> Could you, please, help me make MSIE see the correct value that is
              >'Ionut
              >RUSUBOCA'
              >> ? ( like Netscape )
              >>
              >> Which browser are not W3C compliant in this matter ?
              >>
              >> Thank you,
              >> rivisa
              >>
              >>
              >
              >
              

Maybe you are looking for