Blogger The Remote Server Returned An Error 400 Bad Request
Contents |
when using CloudMediaContext with Azure Media Services ★★★★★★★★★★★★★★★ David Bristol [msft]June 8, 20120 0 0 0 When I was
The Remote Server Returned An Error 400 Bad Request Google-api
developing my first Azure Media Services application based on the how-to guide, the remote server returned an error 400 bad request at system net httpwebrequest getresponse I had a problem when I tried to initialize the CloudMediaContext. I was using code similar to: string
The Remote Server Returned An Error 400 Bad Request Wcf
accountName = "MyAccount";string accountKey = "abcdef12-3456-7890-abcd-ef1234567890";CloudMediaContext mediaContext = new CloudMediaContext(accountName, accountKey); I got the following error when initializing the CloudMediaContext in Visual Studio: WebException was unhandledThe remote server returned an the remote server returned an error (502) bad gateway error: (400) Bad Request. I used Fiddler, http://www.fiddler2.com/, to trace the SSL traffic between my client and the server and found that I was getting the error: "error":"invalid_client","error_description":"ACS50012: Authentication failed. This led me to realize that most likely the problem was with my account name or account key. I tried a couple of different combinations of IDs and keys and realized the remote server returned an error (413) request entity too large that it was my account key that was incorrect. The first parameter that CloudMediaContext needs is the account name. This is the friendly name that you set on step 10 in the Setup Guide when you ran the PowerShell script Add-MediaServicesAccount and specified the –AccountName parameter. The second parameter that CloudMediaContext needs is the account key. This is the key you got in step 12 in the Setup Guide when you ran the $accountdetails.accountkey command. Note that the incorrect account key at the beginning of this article contains a number of dashes and is actually a GUID. The correct account key should end with an equals sign. I modified my code so that I used the correct account key similar to: string accountKey = "AbCdEfGhIjKlMnOpQrStUvWxYz1234567890="; With this change I was able to get update connect and continue. Tags Azure Media Services Comments (0) Cancel reply Name * Email * Website Follow UsPopular TagsWindows Media Services Windows Media Player Windows Media Services 2008 Azure Media Services Windows Media Services 9 Series Silverlight mms Windows Media ASX Cache/Proxy Proxy REST PHP progressive down
partner via SSL in BizTalk Server 2013 ★★★★★★★★★★★★★★★ Wen-Jun ZhangApril 6, 20150 0 0 0 “Remote server returned error:
The Requested Url Returned Error 400 Bad Request
(400) Bad request” occurs when using Microsoft BizTalk 2013 Accelerator the requested url returned error 400 bad request while accessing for RosettaNet to communicate with partner via SSL in BizTalk Server 2013 Recently one
The Remote Server Returned An Error (407) Proxy Authentication Required. C#
of my customer complained that they could not send messages to their partner when using Microsoft BizTalk 2013 Accelerator for RosettaNet while they were able https://blogs.msdn.microsoft.com/randomnumber/2012/06/08/error-400-bad-request-when-using-cloudmediacontext-with-azure-media-services/ to do it via Microsoft BizTalk Accelerator for RosettaNet 3.0 in BizTalk Server 2004. Nothing seemed to be changed as they simply copied settings from BizTalk Server 2004 to the new version, and they used the same certificate for SSL on both environment. However, we got the “Remote server returned https://blogs.msdn.microsoft.com/apacbiztalk/2015/04/06/remote-server-returned-error-400-bad-request-occurs-when-using-microsoft-biztalk-2013-accelerator-for-rosettanet-to-communicate-with-partner-via-ssl-in-biztalk-server-2013/ error: (400) Bad request” on BizTalk Server 2013 while it was working on BizTalk Server 2004. Via network trace, we managed to see when server side returned Cipher Change Spec and Encrypted Handshake Message, client side (BizTalk Server 2013) finished the connection. But what could cause the abrupt disconnection? Obviously checking certificate was the first priority as the failure was on SSL part. We then reviewed the relevant certificate for HTTPS communication, and surprisingly found the certificate was a self-signed one which was provided by their partner while self-signed certificate is usually not recommended in PROD environment. As no more clue could be found through network trace, we captured some diagnostic data to move forward. Further investigation indicated that there was indeed something to do with the self-signed certificate as the diagnostic trace displayed the remote certificate was invalid. We reviewed the source code of Microso
ASP.NET Community Standup Forums Help Home/ASP.NET Forums/General ASP.NET/Web Forms/Getting "The remote server http://forums.asp.net/t/1957789.aspx?Getting+The+remote+server+returned+an+error+400+Bad+Request+Error returned an error: (400) Bad Request" Erro... Getting "The http://tusharvaja.blogspot.com/2015/06/cloudblobcontainercreateifnotexists.html remote server returned an error: (400) Bad Request" Error [Answered]RSS 2 replies Last post Dec 21, 2013 12:31 PM by prk_in ‹ Previous Thread|Next Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved the remote Threads Support Options Advanced Search Related Links GuidanceSamplesVideos Reply AmitTiw Member 33 Points 26 Posts Getting "The remote server returned an error: (400) Bad Request" Error Dec 20, 2013 02:36 AM|AmitTiw|LINK My sample Code is Here string code="CodeValue"; //This Code i get from url string Url = the remote server ""; string clientid = "974356415804-hj7hgirsi0cmqm9kuk1couhslttardt7.apps.googleusercontent.com"; string redirectTo = "http://localhost:13227/GoogleSingIn/Default.aspx"; string Secret = "bLt8iNUTT0u - skLVM6spBiOp"; string scope = "https://www.google.com/m8/feeds"; Url = "https://accounts.google.com/o/oauth2/token"; string grantType = "authorization_code&scope"; string s = ""; s+= "code=" + code; s+="&grant_type=" + grantType; s+="&client_id=" + clientid; s +="&client_secret=" + Secret; s +="&redirect_uri=" + redirectTo; string postData = (s); HttpWebRequest webRequest = (HttpWebRequest)WebRequest.Create(Url); webRequest.Method = "POST"; webRequest.ContentType = "application/x-www-form-urlencoded"; webRequest.ContentLength = postData.Length; using (StreamWriter requestWriter2 = new StreamWriter(webRequest.GetRequestStream())) { requestWriter2.Write(postData); } HttpWebResponse resp = (HttpWebResponse)webRequest.GetResponse(); string responseData = string.Empty; using (StreamReader responseReader = new StreamReader(webRequest.GetResponse().GetResponseStream())) { responseData = responseReader.ReadToEnd(); } but this give me Bad Request at HttpWebResponse resp = (HttpWebResponse)webRequest.GetResponse(); I am Refering this link to develop google oauth https://developers.google.com/youtube/v3/guides/authentication Please help Amit Kumar Tiwari Reply bbcompent1 All-Star 33694 Points 9417 Posts Moderator Re: Getting "The remote server returned an error: (400) Bad Request"
images into cloud blob storage, while coding I faced thiseasy but interesting issue/error while calling CreateIfNotExists() method of blob/queue/table client. Error screen shot shown below. it says: "An unhandled exception of type 'Microsoft.WindowsAzure.Storage.StorageException' occurred in Microsoft.WindowsAzure.Storage.dll Additional information: The remote server returned an error: (400) Bad Request." While looking into it inner exception, I do not see much help…. Below is my Code snippet: var account = CloudStorageAccount.DevelopmentStorageAccount; /******************* Blob **************************************/ var blobClient = account.CreateCloudBlobClient(); var container = blobClient.GetContainerReference(@"Images"); container.CreateIfNotExists(); //************ Download ****************** var blob = container.GetBlockBlobReference(@"CompanyLogoUpload.jpg"); string inputblobname = @"D:\Junk\Logo_Uplaod.jpg"; using (FileStream stream = new FileStream(inputblobname, FileMode.Open)) { blob.UploadFromStream(stream); } Highlighted in RED lines give above error…. Resolutions: Error message is misleading as it says "400-Bad Request", so we might go and verify Azure Connectivity, are we connecting to right subscription, login credentials, etc.. . But the problem was, I gave Container name which starts with Capital letter e.g. Images. Azure does not allow capital letter in container name. I changes this to images, and it worked. When you create a container from UI, error is very descriptive and you do not face this issue, but this comes only when you create container from code behind. Easy but good to know !!!! You can also refer at https://msdn.microsoft.com/en-us/library/dd135715.aspx for more details. Posted by Tushar Vaja at 5:52 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Azure Storage 2 comments: Muhammad Rehan QadriMay 31, 2016 at 9:38 AMThanks a lotReplyDeleteAnonymousJuly 1, 2016 at 2:22 AMThank you!ReplyDeleteAdd commentLoad more... Home Subscribe to: Post Comments (Atom) About Me Tushar Vaja View my complete profile Blog Archive ▼ 2015 (1) ▼ June (1) CloudBlobContainer.CreateIfNotExists gives "The re... Simple template. Powered b