full path post back issue

Discussion in 'ASP.NET / ASP.NET Core' started by jderrigan, Jul 14, 2005.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. This Tuesday, a strange thing began happening on our site www.forewordmagazine.com - we have several directories setup to help our sales team sell our services to our customers. It works like this: if we want to direct someone to a particular area of our site, we tell them on the phone "ah yes, your interested in our reviews. just visit www.forewordmagazine.com slash reviews".

    Ergo, they land at www.forewordmagazine.com/reviews and the default IIS document is index.aspx is displyed(even though the filename is not displayed, the page appears because index.aspx is the IIS default in our website's configuration).

    Well, we have some initial user responses that we collect in dropdownlists which postback with values that we use to show and hide asp.net panels. It appears that there was a change in the IIS setup recently on our server that stopped this from working properly, when it had worked for over one year and a half on multiple pages.What would happen now is that it would just end up redirectingon postback toa completely resovled URL such as www.forewordmagazine.com/reviews/index.aspx- and THEN the postback would work. The symptom onlyoccured in IE, only started on Tuesday of this week and does not appear to be a problem in the other majorebrowserssuch as FireFox and Netscape.

    If anyone evercome across this error in their own site, please - please report it to discountasp.net Tech Support. After two days of email wrangling with them, I got the standard "it mus be your code" response. Also, I had to implement some crazy redirect include to make the pages perform properly in IE. See the following code snippet that returns your current directory which you can use to build a complete URL including file name, and then redirect (index.aspx is our IIS default document, change that name appropriately for your setup):

    dim i, intdir as integer
    dim currURL as string = Request.Url.ToString()
    ' Separate each part of the url within /'s into an array
    Dim arpath() As String
    arpath = currURL.Split("/")
    For i = 0 To arpath.GetUpperBound(0)
    if arpath(i) = "index.aspx" then
    ' Directory is the one before this, set intdir
    intdir = i - 1
    end if
    Next

    I have to say that I was very disappointed in discountasp.net's Tech Support Team on this issue. It seems that they used to be right on, but now it appears that their standards have been lowered. I am still happy with their hosting solution, just wish their Support Team would return to their previous form.

    Comments on any of this post would be great!

    Thanks,
    joe
    ForeWord Magazine
    www.forewordmagazine.com
     
  2. Bruce

    Bruce DiscountASP.NET Staff

    joe,

    i would have to disagree w/ you that you think our support is not doing an adequate job. Most of our support staffs have decent knowledge of ASP.NET but keep in mind that they are tech support not programmer.

    It is very difficult for a support staff to look at a complex symptom that do no generate any error and provide assistence.

    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
  3. Bruce,
    I am in agreement that lower level support may have been in "too deep" to troubleshoot this issue themselves, but if that was the case, then this issue should have been escalated to a server team or toyour next level of your support model. To just say it was my code and do nothing more, until I objected,wasdisappointing. I still have not got an answer as to why our pagessuddenly stopped working in IE; we had to "hack" around the issue. I don't want to slander the Support Team, so I did not post the emailcommunications on this issue - that being said: I'mgoing to move on and try the forum more often... I just wanted to voice an observation on a very frustrating situation.Thanks forthe good hosting solutions.
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page