Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 04/17/2009 1:43 AM by  Kevin McCusker
Portal URLs with port numbers
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Kevin McCusker
New Member
New Member
Posts:6


--
03/23/2009 5:31 PM

    Hello,

    I've got a question and I'm not quite sure where it belongs or if this is even an issue with the Document Library. We've been using version 3 (3.4.11) in our production and have never encountered any issues. We recently set up a new test environment that minics our production environment.

    In our test environment, the portal URLs look something like this: http://123.45.7.890:00/portalname.

    When uploading a file, adding a folder or even just clicking the "Cancel" link button on the New Item page, the document library posts back and then redirects to the URL minus the port number, which returns an HTTP 403 error. If I add in the port number to the HTTP 403 page and then refresh, I am redirected to the proper location within the Document Library.

    Is this an issue with the Document Library, or is this an issue with our environment?

    Thanks for any assistance.

     

    Peter Donker
    Veteran Member
    Veteran Member
    Posts:4531


    --
    04/01/2009 11:23 AM
    Hi Kevin,

    Interestingly enough these buttons (i.e. submit and cancel) are regular link buttons. DMX does not specify where they should postback to. ASP.NET does that. So in this case I'd say it's a configuration issue.

    Peter
    Kevin McCusker
    New Member
    New Member
    Posts:6


    --
    04/17/2009 1:43 AM

    Hi Peter,

    Thanks for the response. There are times when this works perfectly, but after uploading a few items, the port number is stripped out of the Url.

    We've got the port number set to 81, the proper alias set in the HttpAlias section and the web.config has UsePortNumbers set to true. We haven't experienced this issue in any other module we have, I posted hoping you might have encountered this situation before.

    Thanks, if I end up figuring out what is going on I will update the thread.

    Kevin McCusker

     

    You are not authorized to post a reply.