Owa Bad Request Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: HTTP 400 Bad Request exchange 2013 owa 400 bad request Error for OWA Previous Versions of Exchange > Exchange Previous Versions outlook web app bad request - Outlook, OWA, POP, and IMAP Clients Question 1 Sign in to vote Good afternoon everyone,I have bad request error outlook web access an intersting issue at one of my client sites that I'm hoping to get some insight on. The client in question has an Microsoft Exchange Server 2007
Outlook Email Bad Request
that has been functioning fine for the past couple years. The problem is that when users attempt to access the page:https://server.domain.com/exchangeThey receive an error in Internet Explorer stating "HTTP 400 Bad Request"; however, viewing the web page in an alternative browser in light mode (e.g. Firefox) works perfect.The Exchange server's OWA site works fine http 400 bad request internet explorer if you visit the following address:https://server.domain.com/owaIn the past this occured once because of a patch from Microsoft, but I'm having a hard time ascertaining whether or not this is the case this time or not. My thoughts lead me to believe the error may be IIS related.Does anyone have any input on this issue?Thank you for your time and I look forward to hearing from you.: Michael Thursday, May 01, 2008 10:55 PM Reply | Quote All replies 0 Sign in to vote I am having this same exact issue. I tried to install a new certificate and everything went to heck. I can access the owa lite through Safari, but not internet explorer. I'm just as confused. Friday, May 02, 2008 8:14 PM Reply | Quote 0 Sign in to vote Hearty B, I forgot to mention that we had completed a similar task on our client's Exchange Server a few weeks back. The local certificate was slated to exp
e-Reimbursement Effort Certification and Reporting Technology (ECRT) External Requisition Generator fsaATLAS / SEVIS Guided Expense Tool HRA Human Resources System (HRS) ImageNow/WebNow InfoAccess Interactive Reporting outlook bad request android ISIS Job and Employee Management System (JEMS) Manifest Oracle Identity
Outlook Webmail Bad Request
Manager/IAM Other PDS Online PI Financials Tool Pre-Posting Allocation Tool Resource 25 Shared Financial System
Owa Bad Request After Login
Supported LANs TEAR Voicemail/Telephone WISDMCampus Services Active Directory Adobe Connect Backup & Storage Bucky Backup Kumo UW Madison Box UW-Madison https://social.technet.microsoft.com/Forums/exchange/en-US/5c3b9041-a479-4979-a176-a11e8cbfc55f/http-400-bad-request-error-for-owa?forum=exchangesvrclientslegacy Google Apps Blackboard Collaborate Campus Software Library Charter U Course Guide Course Proposal DARS DATN E-commerce E-Learning Canvas Case Scenario Critical Reader Kaltura Learn@UW Lynda.com Moodle Electronic Lab Notebooks eTEACH Faculty Center GoPrint Identity Finder Lecture Capture Service McAfee Endpoint Encryption Mobile UW My https://kb.wisc.edu/helpdesk/page.php?id=47897 UW System Portal My UW-Madison NetID Login Service Office 365 Qualtrics Scholarships@UW-Madison SSL Certificate Student Center UW Digital ID UW White Pages / Directory Web Accessibility Web Hosting WISC Software Catalog WiscAlerts WiscCal WiscList AdvisorList Classlist Mass Email WiscList Custom WiscMail Wisconsin Federation WiscWeb CMSDoIT Help DeskDoIT StaffKnowledgeBaseMiscellaneous General Information SecurityNetworks & Connectivity 2factor (OCIS) VPN Campus Network Departmental VPN eduroam ResNet Wireless UWNet WiscVPNOS and Desktop Applications Applications Browsers Email Clients Productivity Operating Systems Mac OS X Windows PDA/Smartphone VirusSelf Help/Limited Support Eudora Linux/Unix Mac OS 9 Windows 95/98/NT/2000 AdvancedTopics Map > OS and Desktop Applications > Applications > BrowsersWeb Browsers - How to Fix a "Bad Request" ErrorThis document describes what to do if you receive a 400 Bad Request error message upon loading a website.Problem When you attempt to access a website, you ma
Follow 43 Mentions12 Products Neal (Exclaimer) Sales & Marketing Manager https://community.spiceworks.com/topic/683470-exchange-2013-owa-400-bad-request GROUP SPONSORED BY EXCLAIMER TECHNOLOGY IN THIS DISCUSSION Microsoft 493178 http://stackoverflow.com/questions/24736043/response-bad-request-in-html-body-from-ms-exchange-owa Followers Follow Microsoft Windows Server Microsoft Windows Server 2012 Microsoft Exchange Server 2013 Join the Community! Creating your account only takes a few minutes. Join Now Scenario: Exchange 2007/2013 Coexistence One Exchange 2007 Server One Exchange 2013 Server bad request Std, Windows 2012 All mailboxes moved to 2013 - November 27-30 2014 All public folders moved to 2013 - December 2, 2014 Exchange 2007 is still running and has not been removed from the domain, yet. SSL Certs are current for: Autodiscover.ExtDom.com, ex13.ExtDom.com, ex13.IntDom.com Applied CU6 (Dec 3, 2014) to fix owa bad request Mobile access issues. Since applying CU6, OWA does not work with the exception of mobile browsers (Chrome - Nexus 7) or Safari 5.1.7 on Windows 7. These browsers get the OWA 2010 theme (Yellow). User logs into OWA with Domain\UserName and PWD(IE). After clicking Sign In, page returns Bad Request. No errors logged in w3scv logs. All users can connect using Outlook 2013 or Mobile (iPhone & Android) Exchange Admin Center (ECP) still works! Browsers tested: IE10 (windows 7 x64),Chrome 39.0.2171.71m, Opera 26.0, FireFox 34.0.5, Safari 5.1.7 Attempted: https://ex13.ExtDom.com/owa https://ex13.IntDom.com/owa https://ex13.ExtDom.com/owa?ExchClientVer=15 https://ex13.IntDom.com/owa?ExchClientVer=15 https://localhost/owa (on Ex 2013 server) https://localhost/owa?ExchClientVer=15 (on Ex 2013 Server) Fixes attempted: -remove | create Virtual Directories for OWA -Change authentication through Exchange PowerShell - Integrated/Basic from FBA/Basic -reverted since change didn’t work. -Run UpdateCas.ps1 -Run UpdateConfigFiles.ps1 -IISReset (iisReset /NoForce fails) OWA (Default Web Site) displays as Version 15.0 (Build 995.29) in EAC. Links used for troubleshooting: http://community.spiceworks.com/topic/514617-exchange-2013-unable-to-login-to-owa-ecp https://social.technet.microsoft.com/Forums/ie/en-US/f8aa95d4-19e4-483c-8c4b-b039ab0d0127/400-bad-r
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 about hiring 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 community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Response 'Bad request' in HTML-body from MS Exchange OWA up vote 2 down vote favorite 1 I create android app with WebView inside myActivity. public void onCreate( Bundle savedInstanceState) { super.onCreate( savedInstanceState); // before setContentView CookieSyncManager.createInstance( this); CookieSyncManager.getInstance().startSync(); CookieManager.getInstance().removeAllCookie(); CookieManager.getInstance().setAcceptCookie( true); setContentView( R.layout.browser); webviewHTML = (WebView) findViewById( R.id.webviewHTML); WebSettings webSettings = webviewHTML.getSettings(); webSettings.setSupportZoom( true); webSettings.setBuiltInZoomControls( true); webSettings.setJavaScriptEnabled( true); webSettings.setJavaScriptCanOpenWindowsAutomatically( true); webSettings.setAppCacheEnabled( false); webSettings.setSaveFormData( false); webSettings.setSavePassword( false); webSettings.setDefaultTextEncodingName( "utf-8"); webSettings.setDomStorageEnabled( true); webSettings.setUserAgent( 0); webviewHTML.setWebViewClient( new myWebViewClient()); webviewHTML.addJavascriptInterface( new myJavaScriptInterface(), getString( R.string.sAppName)); webviewHTML.setOnLongClickListener( onWebViewLongClickListener); webviewHTML.loadUrl( "myaddress"); } When create WebView I open page of my corporate Microsoft Exchange 2010 OWA 'https://mail.mydomain.com/owa/': Then I manual enter username and password from my domain. But I get error message page inside WebView (response code 200):
Bad Request Screenshot: But when I open this page inside any browser (Chrome) I correct enter to OWA mail page: Why Exchange server return html-page with error inside body? What I need add to WebView properties? Add: Also when I open this page in desktop browser on PC window for username and password popup inside browser (not site): Add solution I find my error. I check URL in WebView.myWebViewClient.onPageFinish and URL was different with my starting URL. I correct this URL and my