Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Urgent - DNN Ajax calls breaking on ServerUrgent - DNN Ajax calls breaking on Server
Previous
 
Next
New Post
11/11/2013 8:35 PM
 
Joey Turks

Joined: 8/15/2012
Posts: 34

Thanks Wes again but that is extremely frustrating.

Looking at how the site is behaving it may be true since all the other .Net applications on the server utilizing the same technologies are fine. DNN seems to be resolving the portal alias' across the site differently for example the login page on postback goes to the wrong alias, the tabs are correct, profile image correct depending on the primary portal alias, host settings clear cache incorrect. In general it seems to me as if all ajax calls retrieve the wrong alias but postbacks are fine. 

For the DNN application that I setup only the binding in IIS 7 is to have a ports but the application itself has it's own domain and sits on port 80. There's no reason why I should be getting this inconsistent behavior. And if it's true that DNN only works on standard ports or even effects an application then that is a beyond me. While previously working on DNN 2 and 3 I never had these issues. 

After considering professional licenses it looks like it's right back to the drawing board.

 
 
New Post
11/11/2013 9:22 PM
 
Wes Tatters


Wes Tatters's Avatar

Joined: 4/30/2004
Posts: 2155

Im really not exactly sure what the fascination is with non standard ports - why exactly do you need to use a port other than 80 in this currently day and age ... its not like the old days where IIS had issues mapping multiple servers. Now you can just bang in a new .local domain and bind it on the same PORT - and whats more - then be testing the exact same environment as your live server - not one with different parameters.

But regardless - have a look at the calls that are being made using something like Fiddler - I'm pretty sure that what you will see is the ajax calls either stripping out the port number from the domain or injecting the wrong root alias - my money is on the port though.  

If this is the case - lodge a support ticket at https://dnntracker.atlassian.net/secu...

It could also be something to do with the friendly url handler - I know at one point there was some issues with how it handled non standard ports - but thought that was mainly to do with SSL.

Again - would be helpful to know exactly what the issue is in your case - fiddler is the best place to start - and look at the raw urls of the AJAX calls.

The process of handling non standard ports is greatly complicated by things like friendly urls and dynamic aliases - its not a simple process - there are literally hundreds of thousands of lines of code happening behind the scenes to make things like ajax look simple and easy to the end user - in this case it might be just one line of that code that is an issue.

FWIW - ajax and complex services plus things like friendly urls did not even really exist as a part of DNN2 - DNN5 - with much of the latest technologies only really arriving in dnn 7.x.

Westa
 
New Post
11/11/2013 9:40 PM
 
Wes Tatters


Wes Tatters's Avatar

Joined: 4/30/2004
Posts: 2155
PS there used to be other arguments for avoiding non standard ports with ajax that related to it basically be blocked on some browsers
- don't believe that in itself is the case here - but by chance what brower are you using?

Westa
 
New Post
11/11/2013 9:48 PM
 
Wes Tatters


Wes Tatters's Avatar

Joined: 4/30/2004
Posts: 2155

Ummm - just had a random thought - have you actually told dnn to allow the use of non standard ports.

By default - for performance reasons non-standard ports are turned off - you need to make a change in the web.config file to tell DNN that it is ok to use them:

http://www.dnnsoftware.com/wiki/Page/AppSettings

And more specifically:

http://www.dnnsoftware.com/wiki/Page/...

you need to enable the line in the webconfig  that contains  --    key="UsePortNumber" value="true"   --
  on a standard  dnn site it will be commented out.

Westa
 
New Post
11/11/2013 10:41 PM
 
Joey Turks

Joined: 8/15/2012
Posts: 34

I can confirm it's an issue with the ports. As soon as I use port 80 all is good. Still in our environment port 80 is not an option so unfortunately it means I'll have to see if I can fix it. I have no idea why changing a port number would break an application and it's very worrying indeed.

I  did use the UsePortNumber to get it working in the DNN site with the port number, without it I'd only be getting 404's errors. The browsers I'm using are IE, Firefox and Chrome all with the same problem.

Again, thanks for you help Wes.
 
 Page 2 of 4
Previous1234Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Urgent - DNN Ajax calls breaking on ServerUrgent - DNN Ajax calls breaking on Server


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out