I doubt this is an issue with Cherokee and most likely a known issue with Mono that could very well be fixed in HEAD, though I'll need to verify that to be certain. The issue I'm referring is noted by Demis Bellott in the ServiceStack release notes found at: https://github.com/ServiceStack/ServiceStack/wiki/Release-Notes (last paragraph of the latest (2.07) release notes.))
*Known issues on MONO*: - Depending on your setup a url with a trailing path '/' will cause Nginx/FastCGI or Apache/mod_mono to request a /default.aspx which if it doesn't exist will return a 404 - If you want to use a custom path i.e. /api your ASP.NET virtual path also needs to start with your httpHandler path. Which is why an ASP.NETapplication hosted on /ApiPath35/api works as expected whilst one at /CustomPath35/api does not. I would start with the above two known issues first and see where that leaves things. More below... On Thu, Mar 24, 2011 at 2:04 AM, Aarón <[email protected]> wrote: > > And I launch the fastcgi-mono-server4 with the next command from the > console: > > sudo fastcgi-mono-server4 > /applications=/myapplication/:/srv/www/htdocs/myapplication/ /socket=tcp: > 127.0.0.1:9000 /stopable=TRUE /filename=/temp/cherokee-mono.socket > /logfile=/home/aamarber/mono-server4.log > > When I put this in the browser: localhost/myapplication it says HTTP 500 > The value for the name controller must be a non-empty string; that's OK, > because myapplication is an api. > > But if I put localhost/myapplication/websites/getwebsites it says the 404 > error. > The above fits fairly well into at least one, if not both of the above mentioned issues which leads me to believe you're problem has likely been located. A short term fix should be fairly straight forward. A long term fix has to come via an upcoming release of Mono. Of course that's assuming that your problem has been properly identified. If it hasn't then I would need more info from you e.g. a properly sanitized and safe for public display copy of your Web.config file would be the most helpful. > I also tried with this example of msdn: > http://archive.msdn.microsoft.com/aspnetmvcsamples/Release/ProjectReleases.aspx?ReleaseId=3547 > > It happens something different, the index page it's shown but when I click > a link, it says 404 error. > Which would be the expected (incorrect) behavior if one or both of the above issues matches your particular case. > What can I do?? Thanks a lot! > If the issue is still unknown and you can safely push a sanitized copy of your Web.config into the public space then lets start there and see where that leads us. -- /M:D M. David Peterson Co-Founder & Chief Architect, 3rd&Urban, LLC Email: [email protected] Mobile: (801) 742-1064 http://3rdandUrban.com | http://amp.fm | http://broadcast.oreilly.com/m-david-peterson/
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
