« Previous Next »

Thread: Unable to get MS-FP/4.0 in MS-Author-Via header using Frontpage Server Extensions

Last post 09-24-2008 6:08 PM by robmcm. 2 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (3 items)

Sort Posts:

  • 07-25-2008, 2:24 AM

    • Manasa82
    • Not Ranked
    • Joined on 07-25-2008, 6:15 AM
    • Posts 1

    Unable to get MS-FP/4.0 in MS-Author-Via header using Frontpage Server Extensions

    When Frontpage Server Extensions 2002 is installed on IIS 6.0, am unable to get Frontpage authoring MS-FP/4.0 in MS-Author-Via header field, when HTTP OPTIONS request is sent.

     I enabled Frontpage Server Extensions using Web extensions node, and also set the Frontpage Web property to "TRUE" in metabase.xml file in IIS.

    Our setup is as below:

    Platform: Windows Server 2003 R2

    IIS 6.0

     Is there any workaround to be done like changes in configuration.

  • 07-29-2008, 6:49 AM In reply to

    Re: Unable to get MS-FP/4.0 in MS-Author-Via header using Frontpage Server Extensions

    Hi Manasa82,

    Do you have WebDAV enabled together? If you WebDAV too, you could see an order strings in MS-Author-Via header like those in

    http://msdn.microsoft.com/en-us/library/cc250217.aspx 

    Zhao Ji Ma
    Sincerely,
    Microsoft Online Community Support

    “Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
  • 09-24-2008, 6:08 PM In reply to

    • robmcm
    • Top 50 Contributor
    • Joined on 05-27-2006, 1:05 AM
    • Redmond, WA
    • Posts 125

    Re: Unable to get MS-FP/4.0 in MS-Author-Via header using Frontpage Server Extensions

    FYI - There have been situations where this header is not being returned correctly. The problem usually stems from the httpext.dll extension not processing the metabase correctly and then caching the incorrect information. Restarting IIS will usually resolve the problem, but your best bet is to add a custom HTTP header with the correct value as described in the following Microsoft KB article:

    http://support.microsoft.com/kb/304133

     

    Robert McMurray (MSFT, IIS)
Page 1 of 1 (3 items)
Microsoft Communities