Generic System Error 401

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 company Business Learn more

Http 403

about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users http 404 Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping

Http 200

each other. Join them; it only takes a minute: Sign up 403 Forbidden vs 401 Unauthorized HTTP responses up vote 1102 down vote favorite 284 For a web page that exists, but for which a user that does 400 error not have sufficient privileges, (they are not logged in or do not belong to the proper user group), what is the proper HTTP response to serve? 401? 403? Something else? What I've read on each so far isn't very clear on the difference between the two. What use cases are appropriate for each response? http-headers http-status-code-403 http-status-codes http-status-code-401 http-response-codes share|improve this question edited Nov 17 '15 at 13:24 MK-rou 107 asked Jul 21 '10 at 7:21 VirtuosiMedia http 500 15.6k1678124 7 401 'Unauthorized' should be 401 'Unauthenticated', problem solved ! –Christophe Roussy May 17 at 12:33 3 Wow. The answers below are ridiculously all over the map. It seems that the correct answer is undefined for non-HTTP authentication. –Joe Lapp Jun 7 at 19:30 add a comment| 11 Answers 11 active oldest votes up vote 1673 down vote accepted A clear explanation from Daniel Irvine: There's a problem with 401 Unauthorized, the HTTP status code for authentication errors. And that’s just it: it’s for authentication, not authorization. Receiving a 401 response is the server telling you, “you aren’t authenticated–either not authenticated at all or authenticated incorrectly–but please reauthenticate and try again.” To help you out, it will always include a WWW-Authenticate header that describes how to authenticate. This is a response generally returned by your web server, not your web application. It’s also something very temporary; the server is asking you to try again. So, for authorization I use the 403 Forbidden response. It’s permanent, it’s tied to my application logic, and it’s a more concrete response than a 401. Receiving a 403 response is the server telling you, “I’m sorry. I know who you are–I believe who you say you are–but you just don’t have permission to access this resource. Maybe if you ask the system administrator nicely, you’ll get permission. But please don’t bo

here for a quick overview of the site Help Center Detailed answers to any questions

Http 503

you might have Meta Discuss the workings and policies of 404 error this site About Us Learn more about Stack Overflow the company Business Learn more about hiring

Postman

developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a http://stackoverflow.com/questions/3297048/403-forbidden-vs-401-unauthorized-http-responses community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up remote server returned an error: (401) unathorized in C# GCM response up vote 0 down vote favorite I have seen this question posted in a thousand places and I have tried all the http://stackoverflow.com/questions/20407296/remote-server-returned-an-error-401-unathorized-in-c-sharp-gcm-response solutions that have worked for others but I am not able to get this to work for me. I used this post as my baseline for the project that Im using (Unauthorized when calling Google GCM). I have tried both the API key and the browser key with no success. Here is my code: using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Linq; using System.Text; using System.Windows.Forms; using System.Web; using System.Net; using System.Net.Security; using System.Security.Cryptography.X509Certificates; using System.IO; namespace GCMTest { public partial class Form1 : Form { public Form1() { InitializeComponent(); } private void button1_Click(object sender, EventArgs e) { string BrowserAPIKey = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxx"; string message = "some test message"; string tickerText = "example test GCM"; string contentTitle = "content title GCM"; string postData = "{ \"registration_ids\": [ \"" + txtRegistrationID.Text + "\" ], \"data\": {\"tickerText\":\"" + tickerText + "\", \"contentTitle\":\"" + contentTitle + "\", \"message\": \"" + message + "\"}}"; string response = SendG

are https://twittercommunity.com/t/error-401-unauthorized/49661 very similar to those sent from my system, but the answer I returned: Error on remote server (401) Not http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec599354.aspx authorized. Nose that I may be missing or I'm doing wrong. If someone could help me I would appreciate generic system very much. Here I have the complete code for my project: using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Linq; using System.Text; using System.Windows.Forms; using System.Net; using System.IO; using System.Diagnostics; using System.Security.Cryptography; using Newtonsoft.Json.Linq; using System.Globalization; generic system error using LinqToTwitter; using System.Security.Policy; using System.Security.Cryptography; namespace TWITER { public partial class Form1 : Form { public Form1() { InitializeComponent(); } private void btnEnviarPost_Click(object sender, EventArgs e) { m_EnviaMensajeUsuario("Send Message", "UsuarioPruebas"); } public void m_EnviaMensajeUsuario(string sMsg, string sScreenName) { var oauth_consumer_key = "DC0sePOBbasdC8r4Smg"; var oauth_signature_method = "HMAC-SHA1"; var oauth_timestamp = GenerateTimeStamp(); var oauth_nonce = GenerateNonce(); var oauth_version = "1.0"; var oauth_token = "3xxxxxxxxxxxJqUxzHoC59wy"; var oauth_consumer_secret = "IhqbdxxxxxxxukA3l49UzpvxGM52"; var oauth_token_secret = "ZO1zxxxxxxxxWSRjrb1zF"; string surl = "https://api.twitter.com/1.1/direct_messages/new.json"; var postBody = "text=" + Uri.EscapeDataString(sMsg) + "&screen_name=" + Uri.EscapeDataString(sScreenName); string baseFormat = "oauth_consumer_key={0}&oauth_nonce={1}&oauth_signature_method={2}" + "&oauth_timestamp={3}&oauth_token={4}&oauth_version={5}&{6}"; string baseString = string.Format( baseFormat, oauth_consumer_key, oauth_nonce, oauth_signature_method, oauth_timestamp, oauth_token, oauth_version, Uri.EscapeDataString(postBody) ); var oauth_signature = CalculateSignature(oauth_consumer_secret, oauth_token_secret, surl, baseString); var headerFormat

productResults.length + resourceResults.length > 0 ? 'See all Search Results' : 'Full site search'}} > > CA Support Online > Support by Product > Support by Product Clarity 13.2.0 Generic Patch available to resolve reported issues Document ID:TEC599354 Last Modified Date:10/03/2014 {{active ? 'Hide' : 'Show'}} Technical Document Details Products CA PPM CA Governance, Risk ＆ Compliance Manager Releases CA PPM:Release:13.2 On Premise Components CLARITY PPM INTEGRATIONS ＆ INSTALLATIONS:PPMENV Description: We recommend customers with Clarity 13.2.0 implementations to install the current Clarity 13.2.0 Generic Patch if they are interested in obtaining resolutions to the issues identified below. Solution: Patches are intended to be timely fixes and are not fully regression or integration tested, and are only tested against the issues listed below. CA feels confident that this patch will resolve the addressed problems, but customers should be aware that a patch could have adverse side effects to the function of their Clarity application. Customers should not apply patches directly to production systems without first verifying in a test environment. If any issues arise in the installation or use of this patch, please contact CA Support. A list of the fixes resolved with this Generic Patch can be found in the 'Readme' documentation included in the 'jar' file. Version/Build: 13.2.0.472 09 04 Documentation: Readme.txt Released On: September 17, 2014 Resolved Issues in This Release: CLRT-74271: Allocation discrepancies using %Availability vs FTE on Resource Workload vs Weekly Detail portlets CLRT-73928: Post Timesheets Job generates NullPointerException Error when attempting to calculate the Task Assignment Actual Cost value (TEC605969) Resolved Issues in Previous Release: CLRT-74665: User with basic access in Clarity is able to access Team Staff and Team Detail page of any project by tampering the URL (TEC613363) CLRT-74536: Internal network error on Microsoft Windows results in "Unable to process request - server