GetResource.ashx inserting domain name with funky port in CSS

Bryan Drenner asked on September 10, 2014 18:18

After upgrading from Kentico 6 to Kentico 8, GetResource.ashx is mucking up our CSS by inserting our domain name with an invalid port number (4433) wherever there's a url(...) value. I read in this article that we can hack GetResource.ashx.cs, but that file does not exist in our solution. Turning off CSS minification via Settings > Performance > Resources does not work either.

Recent Answers


Brenden Kehren answered on September 10, 2014 20:08

Were there any customizations to your 6.x install that would cause that rewrite with the port?

0 votesVote for this answer Mark as a Correct answer

Bryan Drenner answered on September 10, 2014 20:11

No.

The site is behind a load balancer, and port 4433 is somehow involved, but http://www.newvictory.org:4433 is not meant to be publicly accessible. It seems like Kentico somehow sees that port and is mistakenly using it.

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on September 11, 2014 06:20

Is it in the site URL at all in the Sites app? How is IIS configured? Is it specifying a port in the bindings? Have you checked to see what the load balancer settings are or what the IIS logs show? I'm willing to bet the load balancer or IIS aren't configured correctly.

0 votesVote for this answer Mark as a Correct answer

Bryan Drenner answered on September 11, 2014 16:28

I don't fully understand our setup, but here's what I've been told:

First of all, our Kentico instance serves multiple sites, several of which use SSL. The Kentico instance is hosted by an AWS EC2 instance. I've been told that some limitation of AWS, IIS, and SSL certificates requires that each site has a unique SSL port binding. The sites sit behind a load balancer that simply redirects port 443 to the actually bound ports.

Unfortunately, I'm no expert in SSL certificates and load balancers. In lieu of a solution I had to pull all of our CSS out of Kentico.

0 votesVote for this answer Mark as a Correct answer

Bryan Drenner answered on September 11, 2014 21:58

We figured out how to have the load balancer route the weird ports in addition to 443, so even though the CSS is screwed up, it still works. Time to put my CSS back in the CMS.

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on September 12, 2014 14:04

So sounds like maybe someone "fat fingered" the port number on configuration? ;) We all make mistakes, just sucks we have to debug for so long to figure it out!

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.