Misconfigured server
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 |
|
Monday, May 10, 2010, 7:33:22 PM |
0
|
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? |
||||
|
0
|
The response data in Fiddler was less than useless: it merely told me that the server threw a 405 error. |
||||
|
0
|
Can you post a sample of your calling script? |
||||
|
0
|
Calling section: |
||||
|
0
|
Please send an email to support at countersoft dot com and we will remote into your PC to see if we can sort it. |
||||
|
0
|
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. |
||||
|
0
|
Problem fixed. |
||||
|
0
|
Thanks for the confirmation. Glad all is well now. |
||||
|