Domain/IIS problem

742 views
Skip to first unread message

Stephen Jones

unread,
Sep 28, 2009, 11:45:17 AM9/28/09
to XMPie Interest Group
I have come up against a problem that i have never seen before. I have
setup a domain for a campaign - all fine, all forwarding is fine, a
user can get to a purl but when they click submit they are presented
with 'This domain is not configured for this service. Please contact
the webmaster to have it enabled.'

I have contacted the company who hosts the domain and said everything
is OK at their end.

Any ideas???

I thought it may be something with IIS or similar in delivering the
campaign. Other campaigns that are on the same uProduce server are
working fine.

Timothy Perrett

unread,
Sep 28, 2009, 11:56:16 AM9/28/09
to XMPie Interest Group
Stephen,

If your getting that IIS error then its an IIS problem :-) Check the
following:

- name of the domain you configured in IIS
- permissions on the folders
- make sure you assigned the process and anonymous IIS users

If you have a mac hanging around run:

curl -I http://domain.com

If your having a problem, you'll see something like:

HTTP/1.1 403 Forbidden
Date: Mon, 28 Sep 2009 15:50:36 GMT
Server: Apache
Content-Type: text/html; charset=iso-8859-1

Does that help? Also, can you paste the helicon rule?

Cheers, Tim

Bill

unread,
Sep 28, 2009, 2:30:02 PM9/28/09
to XMPie Interest Group
I recently ran into a problem which looks... a little diffent ;-)

A prospect customer of us bought a domain name. Via their domain
broker company, they mapped the new domain name to our XMPie server's
IP address.

While browsing the domain seemed to properly route to our server,
Helicon-based PURLs failed (error 404).

An investigation showed that our customer configured their domain with
process named "Web Redirection" (which is usually used to map a domain
name to another one, while our customer used it to map the domain name
to our IP address). So, when the HTTP request reached our server, the
domain name was already replaced by our IP address, thus misleading
Helicon (which was expecting the domain name, not an "hardcoded" IP
address).

Creating a "Type A" record in the domain's DNS Zone immediately fixed
the issue.

This to say that when a "company who hosts the domain [says]
everything
is OK at their end", it can be true, but it can be also wrong...

Stephen Jones

unread,
Sep 28, 2009, 4:07:44 PM9/28/09
to XMPie Interest Group
Tim,

Helison rule:
RewriteCond %{HTTPS} off
RewriteCond %{HTTP_Host} (^(?:www\.)?www.openevenings.net$) [NC]
RewriteRule ^/([^/]+\.(?:html|htm|aspx|asp|jpg|jpeg|gif|css|png|txt|
ashx|js|ascx|flv|swf|ico|xml))$ http://127.0.0.1/COSC/$1?XMPieOrgBaseURL=http://%1/$1
[NC,L,P,QSA]

RewriteCond %{HTTPS} off
RewriteCond %{HTTP_Host} (^(?:www\.)?www.openevenings.net$) [NC]
RewriteRule ^/([^/]+)$ http://127.0.0.1/COSC/Landing.aspx?PURL=$1&XMPieOrgBaseURL=http://%1/
[NC,L,P,QSA]

RewriteCond %{HTTPS} on
RewriteCond %{HTTP_Host} (^(?:www\.)?www.openevenings.net$) [NC]
RewriteCond %{REQUEST_URI} !^/(robots\.txt|favicon\.ico)$
RewriteRule ^/([^/]+)$ https://www.openevenings.net/COSC/Landing.aspx?PURL=$1
[NC,L,R]

RewriteCond %{HTTPS} off
RewriteCond %{HTTP_Host} (^(?:www\.)?www.openevenings.net$) [NC]
RewriteRule ^/([^/]+/.*)$ http://127.0.0.1/COSC/$1?XMPieOrgBaseURL=http://%1/$1
[NC,L,P,QSA]


Looking at everything else seems fine.

Bill - feedback on your comments I can see where you are coming from,
I control the Domain Management through web access and a record is
direct and not redirected as per suggestion.

SJ
> > working fine.- Hide quoted text -
>
> - Show quoted text -

Timothy Perrett

unread,
Sep 28, 2009, 4:36:16 PM9/28/09
to XMPie Interest Group
Stephen,

You have something more fundamental wrong here - http://www.openevenings.net/
doesn't even resolve to a basic index.html... If you get that working,
then you'll find your solution there without doubt.

Your getting a 403 on that domain which tells me something is very
wrong with your IIS config.

Cheers, Tim

On Sep 28, 9:07 pm, Stephen Jones <jonesy67...@googlemail.com> wrote:
> Tim,
>
> Helison rule:
> RewriteCond %{HTTPS} off
> RewriteCond %{HTTP_Host} (^(?:www\.)?www.openevenings.net$) [NC]
> RewriteRule ^/([^/]+\.(?:html|htm|aspx|asp|jpg|jpeg|gif|css|png|txt|
> ashx|js|ascx|flv|swf|ico|xml))$http://127.0.0.1/COSC/$1?XMPieOrgBaseURL=http://%1/$1
> [NC,L,P,QSA]
>
> RewriteCond %{HTTPS} off
> RewriteCond %{HTTP_Host} (^(?:www\.)?www.openevenings.net$) [NC]
> RewriteRule ^/([^/]+)$http://127.0.0.1/COSC/Landing.aspx?PURL=$1&XMPieOrgBaseURL=http://%1/
> [NC,L,P,QSA]
>
> RewriteCond %{HTTPS} on
> RewriteCond %{HTTP_Host} (^(?:www\.)?www.openevenings.net$) [NC]
> RewriteCond %{REQUEST_URI} !^/(robots\.txt|favicon\.ico)$
> RewriteRule ^/([^/]+)$https://www.openevenings.net/COSC/Landing.aspx?PURL=$1
> [NC,L,R]
>
> RewriteCond %{HTTPS} off
> RewriteCond %{HTTP_Host} (^(?:www\.)?www.openevenings.net$) [NC]
> RewriteRule ^/([^/]+/.*)$http://127.0.0.1/COSC/$1?XMPieOrgBaseURL=http://%1/$1
Reply all
Reply to author
Forward
0 new messages