I am trying to wire up a Rest Extension but am having no luck - I have coded \base functionality before with no problems and this is making me pull my hair out (what's left of it).
The error message is;
The page cannot be displayed because an internal server error has occurred.
My code is
using System; using System.Collections.Generic; using System.Linq; using System.Web; using System.Xml; using umbraco.presentation.umbracobase;
namespace Foodstuffs.Umbraco.Trents { [RestExtension("restExt")] public class RestHelper { [RestExtensionMethod()] public static string CheckCustomerNumber(string custNo) { ... }
} }
I am trying to call the rest extension via the following URL:
\base Internal Server Error Problem
Hi there
I am trying to wire up a Rest Extension but am having no luck - I have coded \base functionality before with no problems and this is making me pull my hair out (what's left of it).
The error message is;
My code is
I am trying to call the rest extension via the following URL:
http://myURL/base/restExt/CheckCustomerNumber/123.aspx
I have tried using a capital B in base too but that didn't work either
Please, please, please tell me what obvious piece of the puzzle I am missing...
Nigel
What is the actual server error ? Maybe it's caused because it's an error in your method
Hi Nigel,
As dawoe said, this is typically something going wrong in the method - most common error is a nullpointer exception :-)
- Bo
Hey
Thanks for your input dawoe / Bo
I haven't managed to find anything in the IIS logs yet. There is nothing in the Umbraco log table of use.
I will "strip" out my code and do a "Hello World" and see how it goes from there.
Thanks again.
Nigel
Bo - bang on with suggestion....
Mucky code was the problem, guess I was expecting more of an useful error message rather than just "dying"
N
Hi Nigel,
No problem there :-)
As for the no-exception pondering, I think it may be due to /base being just a proxy between the client and the server. I may be wrong though.
- Bo
Hi Nigel,
Probably you have your custom errors set to on or remote only, that's why you don't see the error
is working on a reply...