Network Error 501 Not Implemented
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the
501 Error Message
company Business Learn more about hiring developers or posting ads with us Stack Overflow error 501 android Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2
501 Not Implemented Ajax
million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Why do I get this 501 Not Implemented error? up vote 3 down vote favorite I am performing the error 501 youtube following AJAX call: $(document).ready(function() { $.getJSON('https://sendgrid.com/api/user.stats.json', { 'api_user': 'me@mydomain.com', 'api_key': 'MYAPIKEY', 'user': 'me@mydomain.com', 'category': 'MY_CATEGORY' }, function(response){ alert('received response'); } ); }); and I get no alert message as expected. Instead, Firebug says I get "501 Not Implemented." Why? What do I need to do to fix this? If I go to the URL corresponding to the AJAX call in Firebug, I get a JSON file as a download, and it contains the http 501 error fix expected data. One thing I've noticed is that firebug says OPTIONS instead of GET: ajax json share|improve this question edited Jun 25 '10 at 21:15 asked Jun 25 '10 at 21:06 Chad Johnson 7,5802275136 add a comment| 3 Answers 3 active oldest votes up vote 2 down vote accepted I don't know if this is related, but generally when requesting JSON on the client to a server in a different domain you'll need to use JSONP instead of JSON due to the Same Origin Policy. Unfortunately, it doesn't appear that their API supports using JSONP -- so they must expect you to interact with their site from your server. In that case you'll need proxy methods on your server to translate the calls to their API so that the client calls are made to a server in the same domain as the page. share|improve this answer answered Jun 25 '10 at 21:13 tvanfosson 352k65571700 I am pretty sure this is the problem. JSONP could be an answer. –Chad Johnson Jun 25 '10 at 21:26 Though, now I am realizing that making that call via the client's browser could be very unsafe, since they would have the URL (which contains private information). –Chad Johnson Jun 25 '10 at 21:32 add a comment| up
360 games PC games
Error 501 Email
Windows games Windows phone games Entertainment All Entertainment error 501 youtube update Movies & TV Music Business & Education Business Students & educators
Http/1.1 501 Not Implemented
Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet http://stackoverflow.com/questions/3121451/why-do-i-get-this-501-not-implemented-error Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/247643 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
References & Guides Learning web development Tutorials References Developer Guides Accessibility Game https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/501 development ...more docs Mozilla Docs Add-ons Firefox Developer ToolsFeedback Get Firefox help Get web development help Join the MDN community Report a content problem https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html Report a bug Search Search Languages No translations exist for this article. Add a translation Edit Advanced Advanced History Print this article MDN error 501 Web technology For developers HTTP HTTP response status codes 501 Not Implemented Your Search Results fscholz Jeremie 501 Not Implemented In This Article StatusSpecificationsBrowser compatibility The HTTP 501 Not Implemented server error response code indicates that the request method is not supported by the server and cannot be handled. 501 not implemented The only methods that servers are required to support (and therefore that must not return this code) are GET and HEAD. Note that a 501 error is not something you can fix, but requires a fix by the web server you are trying to access. A 501 response is cacheable by default. Status 501 Not Implemented Specifications Specification Title RFC 7231, section 6.6.2: 501 Not Implemented Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content Browser compatibility The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request. DesktopMobile Feature Chrome Edge Firefox Internet Explorer Opera Safari Servo Basic Support(Yes)(Yes)(Yes)(Yes)(Yes)(Yes)(Yes) Feature Android Chrome for Android Edge Mobile Firefox for Android IE Mobile Opera Mobile Safari Mobile Basic Support(Yes)(Yes)(Yes)(Yes)(Yes)(Yes)(Yes) Document Tags and Contributors Tags: HTTP Server error Status code Co
response. 10.1 Informational 1xx This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions. A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent. Proxies MUST forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).) 10.1.1 100 Continue The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. See section 8.2.3 for detailed discussion of the use and handling of this status code. 10.1.2 101 Switching Protocols The server understands and is willing to comply with the client's request, via the Upgrade message header field (section 14.42), for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response. The protocol SHOULD be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use s