Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Misconfigured server

web-app

Recently, we upgraded a development server to Gemini 3.6.5.  Prior to this upgrade, we had been using a number of in-house scripts to interact with our Gemini installations.

That upgraded installation, however, is now throwing 405 errors.  I've checked the system and it appears that all .ashx handlers have put, get, debug, and head verbs handled.  I've gone through the installation documentation, and everything looks correct, yet obviously nothing works on API requests.

I've tried other verbs using Fiddler to reshape requests.  I had no luck.

Could I get some ideas of what else to check?  Obviously, there's something I'm missing here.

photosinensis
· 1
photosinensis
Replies (8)
helpful
0
not helpful

When using fiddler you should look at the response data it might give us a clue. Did you do that?

Also, make sure that you have enabled all verbs for the ASHX file handler in IIS.

Do you have WebDav installed on the server?


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

The response data in Fiddler was less than useless: it merely told me that the server threw a 405 error.

[code]
HTTP/1.1 405 Method Not Allowed
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html
Expires: -1
Server: Microsoft-IIS/7.0
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
Date: Mon, 10 May 2010 17:57:03 GMT
Content-Length: 1293

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<title>405 - HTTP verb used to access this page is not allowed.</title>
<style type="text/css">
<!--
body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;}
fieldset{padding:0 15px 10px 15px;}
h1{font-size:2.4em;margin:0;color:#FFF;}
h2{font-size:1.7em;margin:0;color:#CC0000;}
h3{font-size:1.2em;margin:10px 0 0 0;color:#000000;}
#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS", Verdana, sans-serif;color:#FFF;
background-color:#555555;}
#content{margin:0 0 0 2%;position:relative;}
.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;}
-->
</style>
</head>
<body>
<div id="header"><h1>Server Error</h1></div>
<div id="content">
 <div class="content-container"><fieldset>
  <h2>405 - HTTP verb used to access this page is not allowed.</h2>
  <h3>The page you are looking for cannot be displayed because an invalid method (HTTP verb) was used to attempt access.</h3>
 </fieldset></div>
</div>
</body>
</html>
[/code]

No, WebDAV is not installed on the server.


photosinensis
· 1
photosinensis
helpful
0
not helpful

Can you post a sample of your calling script?


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Calling section:

[code]
CustomFieldDataEN field = new CustomFieldDataEN();
field.IssueID = issue.IssueID;
field.ProjectID = issue.ProjectID;
field.UserID = issues.WhoAmI().UserID;
field.CustomFieldData = request.ToString();
field.CustomFieldID = id;
return fields.SaveCustomFieldData(field);
[/code]



photosinensis
· 1
photosinensis
helpful
0
not helpful

Please send an email to support at countersoft dot com and we will remote into your PC to see if we can sort it.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Okay, new data from Fiddler.  I took another look at the header and the request.  It looks like the method in question creates a PUT request, but for some reason I haven't isolated yet, the allowed verbs are GET, HEAD, OPTIONS, and TRACE.

I'm currently looking into options, but wouldn't mind a pointer or two.

ETA: I've also taken a look at the config file.  It reflects IIS's settings, which are currently to allow all verbs.  Changing the allowed verbs manually does not affect the allowed verbs on the service.


photosinensis
· 1
photosinensis
helpful
0
not helpful

Problem fixed. 

WebDAV was installed on the server.  Don't know how that happened, as it's not supposed to be there.


photosinensis
· 1
photosinensis
helpful
0
not helpful

Thanks for the confirmation. Glad all is well now.


Saar Cohen
· 5000
Saar Cohen