Hi Richard

Thank you for your reply. I thought that a relative path would work, since it's been described in this WIKI entry with a relative path: http://our.umbraco.org/wiki/reference/packaging/package-actions/community-made-package-actions/add-a-scheduled-task

However when I'm using the full path it also fails. As mentioned the DNS has not been setup yet so I'm currently using the IP so the url looks something like this for instance http://xxx.xx.xx.xxx/mytask.aspx - But I guess that it should be working even though I'm using the IP right? If so...it still does'nt :'-(

/Jan

This is what it does:

 private static bool getTaskByHttp(string url)
        {
            HttpWebRequest myHttpWebRequest = (HttpWebRequest)WebRequest.Create(url);
            HttpWebResponse myHttpWebResponse = null;
            try
            {
                myHttpWebResponse = (HttpWebResponse)myHttpWebRequest.GetResponse();
                if (myHttpWebResponse.StatusCode == HttpStatusCode.OK)
                {
                    myHttpWebResponse.Close();
                    return true;
                }
                else
                {
                    myHttpWebResponse.Close();
                    return false;
                }
            }
            catch
            {
            }
            finally
            {
                // Release the HttpWebResponse Resource.
                if (myHttpWebResponse != null)
                    myHttpWebResponse.Close();
            }

            return false;
        }

So you could try that from your own code and see if you get the correct statuscode back.

Hi Jan,

IP should work indeedd. you can access the page http://xxx.xx.xx.xxx/mytask.aspx  from that server? If it's a normal aspx page and not excluded in the web.config it will throw a 404. So maybe that goes wrong?

Cheers,

Richard

@Morten: Thanks for your help. I've just tested the console app and it returns "true"...So now I'm thinking...what would be the next step?

@Richard: Yes, the page exists :)

/Jan

Turns out that I should just use "localhost". :)

Thanks for your help guys.

/Jan

I imagine localhost will not work in a shared hosting environment (which includes most kinds of test & staging servers)

Just ran into this... CMSImport stopped running when we moved a site to a production server. Which, of course, doesn't have the same URL as the test server.

So... umbraco on the production server kept on triggering the tasks on the test server. A kind of nice but somewhat surprising feature... you could have one umbraco installation run tasks on all your servers this way - with a big umbracoSettings.config file... :)

Not much happened on the production server, though...

Seriously, this is a serious problem that makes staging even more confusing. Is it VERY hard to modify getTaskByHttp so that it accepts paths like "/something" and "~/something" and prepend the relevant beginning of the URL to them (with some backward compatibility in place to leave it as is if it starts with http://)?

I haven't dug deep enough in umbraco to know whether or not backgrund code has access to the (a) site host header. If not, it should be trivial to stick it somewhere in application state on the first request. Not?

vote for this issue here: http://umbraco.codeplex.com/workitem/22757

is working on a reply...