Apex no respond 400 bad request

My computer suddenly had a blue screen of death and restarted, I am trying to log into the apex installed on my laptop and I am getting a 400 bad request, The HTTP client sent a request that this server could not understand.
Any ideas on what might be the problem?

For starters, ensure that the windows services are running. Look for the OracleXETNSListener and the one for the database (something like OracleXEDatabase).

Similar Messages

Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http status code and text is 400, Bad Request.

Hi All,
I am seeing the following error for SMS_AWEBSVC_CONTROL_MANAGER component with Message ID: 8100
Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http status code and text is 400, Bad Request.
awebsctl.log file has below errors:
Call to HttpSendRequestSync failed for port 80 with status code 400, text: Bad Request
SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
13920 (0x3660)
AWEBSVCs http check returned hr=0, bFailed=1
SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
13920 (0x3660)
AWEBSVC's previous status was 1 (0 = Online, 1 = Failed, 4 = Undefined)
SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
13920 (0x3660)
Health check request failed, status code is 400, 'Bad Request'.
SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
13920 (0x3660)
Management point and Application Catalog Website Point are installed on the same Server where I am seeing the error for Application Catalog Web Service Point role. Management Point and Application Catalog Website Point are functioning properly. Application
Catalog Website is working.
Thanks & Regards, Kedar

Hi Jason,
Application Catalog Web Service Point and Application Catalog Website Point; both are installed as per below configuration on same Server:
IIS Website: Default Web Site
Port Number: 80
with default value for Web Application Name configured.
For SMS_AWEBSVC_CONTROL_MANAGER component, I am getting below error in Component Status:
Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http status code and text is 400, Bad Request.
Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which AWEBSVC is configured to communicate.
Solution: Verify that the designated Web Site is configured to use the same ports which AWEBSVC is configured to use.
Possible cause: The designated Web Site is disabled in IIS.
Solution: Verify that the designated Web Site is enabled, and functioning properly.
For more information, refer to Microsoft Knowledge Base.
And awebsctl.log has the below error lines:
Call to HttpSendRequestSync failed for port 80 with status code 400, text: Bad Request
SMS_AWEBSVC_CONTROL_MANAGER
12/23/2014 11:04:36 AM 16388 (0x4004)
AWEBSVCs http check returned hr=0, bFailed=1
SMS_AWEBSVC_CONTROL_MANAGER
12/23/2014 11:04:36 AM 16388 (0x4004)
AWEBSVC's previous status was 1 (0 = Online, 1 = Failed, 4 = Undefined)
SMS_AWEBSVC_CONTROL_MANAGER
12/23/2014 11:04:36 AM 16388 (0x4004)
Health check request failed, status code is 400, 'Bad Request'.
SMS_AWEBSVC_CONTROL_MANAGER
12/23/2014 11:04:36 AM 16388 (0x4004)
STATMSG: ID=8100
What should I check from IIS side?
Application Catalog Website is functioning properly.
Thanks & regards,
Kedar
Thanks & Regards, Kedar

HTTP 400 Bad Request when accessing Oracle XE/Apex from the Internet

I have Oracle Express Edition upgraded to Apex 3.2. I can access everything (SQL prompt, Apex HTTP) from my local machine. I have configured the server for remote access on a non-default (not 8080) port.
I have executed: exec dbms_xdb.setListenerLocalAccess(false);
I can access the server using:
http://coyote:9977/apex (brings me to Application Express Administration Services login screen)
(where "coyote" is the local machine name of my Windows Vista box, where the Oracle/Apex server is installed.)
But when I try:
http://internet_server_name:9977/apex
(where "internet_server_name" is the internet DNS name visible of my machine visible from the internet.)
I get "HTTP 400 Bad Request"
I know the request is hitting the Oracle Listener (getting through firewalls, cable modem router, etc) since the http attempt causes the entry:
20-MAR-2009 20:36:53 * http * (ADDRESS=(PROTOCOL=tcp)(HOST=68.189.244.22)(PORT=52540)) * handoff * http * 0
to be made in the C:\oraclexe\app\oracle\product\10.2.0\server\network\log\listener.log
An attempt using the local (Windows) machine name makes a similar entry in the listener log:
20-MAR-2009 20:47:35 * http * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.7)(PORT=52811)) * handoff * http * 0
This seems like a security issue of some kind (is the server dropping a request from "outside" the local domain?)
I'm new to Oracle so I am not familiar with how to debug this sort of connectivity issue. In case it helps:
LSNRCTL> status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production
Start Date 20-MAR-2009 19:27:00
Uptime 0 days 1 hr. 30 min. 59 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Default Service XE
Listener Parameter File C:\oraclexe\app\oracle\product\10.2.0\server\network\admin\listener.ora
Listener Log File C:\oraclexe\app\oracle\product\10.2.0\server\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC_FOR_XEipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=coyote)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=coyote)(PORT=9977))(Presentation=HTTP)(Session=RAW))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "XEXDB" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Service "XE_XPT" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Service "xe" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
The command completed successfully
Any help appreciated,
john

Hans Forbrich wrote:
CoyoteTech wrote:
I have tried running with the firewall (F-Secure) completely disabled, but it made no difference. I do see the request hit the listener, and the handoff appears to be successful, but it goes silent from there. I also have a cable modem router that has the port forwarding set, but maybe there are other handoff ports besides the initial one (e.g. 8080) that need to be forwarded?Please also check the Windows firewall is off as well. Yes, Windows Firewall is disabled as well. See my previous post to Tyler - I'm pretty sure the reqwuest makes it through the firewall/router layer, since it causes an entry in Listener.log
Is your problem through the router only? In other words, if you try from a second machine that is on the same side as your XE, are you working OK? (My home ISP blocks a bunch of ports. Including SMTP, FTP, Telnet. And 8080 since that is a traditional default for many Java 'servers'.)
Yes, it appears to be related to a non-local IP address. I'm sure it makes it through the router - I also have several other ports that make it through (e.g. port 80).
I have poked around the DBMS_EPG docs, and ran a few of the commands there (list DADS etc). DBMS_EPG was first 'released' to us in 10gR2. As far as I'm concerned, XE is the public 'beta' or 'release candidate'. (This is supported by Oracle's docs that state that Apex using DBMS_EPG is first supported using 10.2.0.3 or 11g.) There are known bugs and there is no way to patch XE to fix them. However, I do not know whether you are hitting those bugs.
http://www.astral-consultancy.co.uk/cgi-bin/hunbug/doco.cgi?11410 provides some good notes.
Interesting. I will check out these docs later today.
>>
What happens when the listener hands off to a registered handler?
http://download.oracle.com/docs/cd/B19306_01/network.102/b14212/concepts.htm#i1049597 gives a good description.
Thanks.
How do I pick up the [log] trail from there?I'm thniking that the listener's log is still the primary way to go. You may need to increase the log or trace level. I have not investigated how to gen or access logs inside EPG.I tried Tyler's trace but did not seem to add additional info to the Listener.log.

APEX 3.1.1.00.09 – HTTP-400 Bad Request

We have some users who are experiencing what appears to be a browser problem in one of our APEX applications.
When clicking on any button that does an insert or update to the database some users get an HTTP-400 Bad Request error message. The database does not get updated and anything they click on after that shows that message. When this happens we have been able to restore the user’s browser to the default settings and the issue is resolved. However, we were not able to isolate which browser setting is causing the issue.
We have seen the issue in IE 6, IE 7 and IE 8. IE 6 must be upgraded and then reset, for 7 and 8 just a reset to default fixes the problem.
Here’s the error we see in the Apache server error log:
mod_plsql: /pls/ax_tastest/wwv_flow.accept HTTP-400 Invalid name
We’d like to determine which of the many browser settings could be causing this.

We got this error when upgrading from Apex 3.1 to 3.2 for our applications that use SSO authentication. This was our resolution (thanks to Scott):
Create schema apex_sso
Install the sso sdk into apex_sso schema (run the loadsdk script)
Connect as SYS from the apex core directory and run:
alter session set current_schema=apex_sso
grant execute on wwsec_sso_enabler_private to apex_030200
grant select on wwsec_enabler_config_info$ to apex_030200
alter session set current_schema=apex_030200
create synonym wwsec_enabler_config_info$ for apex_sso.wwsec_enabler_config_info$
create synonym wwsec_sso_enabler_private for apex_sso.wwsec_sso_enabler_private
drop public synonym wwv_flow_custom_auth_sso
@custom_auth_sso_902.sql
@custom_auth_sso_902.plb
create public synonym wwv_flow_custom_auth_sso for apex_030200.wwv_flow_custom_auth_sso
grant execute on wwv_flow_custom_auth_sso to public
copy rows from wwsec_enabler_config_info$ in flows_030100 table to the same table in apex_sso

HTTP 400 Bad Request

Hello All,
I'm up against a show stopper. I have a simple region (lets call it the "Quote Region") of type SQL Query that returns rows from a table which I will need tp update. Occasionally the query will return a large number of rows, depending on the size of the customer's quote. My problem is when the quote is large (somewhere around 200 rows) and I perform an update I get HTTP 400 Bad Request "the webpage cannot be found", the URL says something about 7779/pls/apex/wwv_flow.accept.
The update is simple, it takes values that a user enters in another region and does a mass update to the lines in the Quote Region. The lines in the Quote region that are updated are determined by the user selecting them in a shuttle with the shuttle returning the line_id. For small quotes and even quotes with up to 195 lines everything works fine but I need this to work for large quotes! Does anyone know what's going on here???
I'm on version 3.1.2.00.02
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
I don't think it's my code, but here is the mass update anonymous block for review...
DECLARE
l_selected APEX_APPLICATION_GLOBAL.VC_ARR2;
x PLS_INTEGER := 1;
c_loopcount NUMBER := 0;
c_labelcount NUMBER := 0;
l_records VARCHAR2(32000);
l_line_id NUMBER;
BEGIN
-- Check that the shuttle has values
If :P3_APPLY_TO_LINES = 'NA' Then
RAISE_APPLICATION_ERROR( -20110, 'At least one line is required.' );
End If;
-- Convert the colon separated string of values in the shuttle into
-- a PL/SQL array
l_selected := APEX_UTIL.STRING_TO_TABLE(:P3_APPLY_TO_LINES);
FOR i IN 1.. NVL(l_selected.count,0) LOOP
l_line_id := l_selected (i);
c_loopcount := c_loopcount +1;
-- loop through each of the label values that have been entered by the user
FOR i IN 1 .. apex_application.g_f11.COUNT LOOP
c_labelcount := c_labelcount +1;
-- Update the transaction table with the provided value
UPDATE forx_label_transactions
SET value = apex_application.g_f01 (i) -- the user supplied value
,last_update_date = sysdate
,last_updated_by = :P3_LAST_UPDATED_BY
,last_update_login = :P3_LAST_UPDATE_LOGIN
WHERE label_id = apex_application.g_f11 (i) -- the hidden label id that is the foreign key
AND source_transaction_id = l_line_id; -- the line id of the quote line
--AND source_transaction_id = 1074016;
END LOOP;
l_records := l_records||l_selected (i);
END LOOP;
:p3_labelcount := c_labelcount;
:p3_loopcount := c_loopcount;
:p3_selected := (l_records);
END;
Edited by: blue4speed on Oct 7, 2010 8:54 PM
Edited by: blue4speed on Oct 7, 2010 9:04 PM

When submitting a page there is some limit about the page size (I think 32K) after that it throws HTTP 400. We were also facing the same problem in our large tabular form. You can use Pagination to limit the rows displayed in a page to avoid this error.
But when using pagination you will face another issue. Let's say you have 100 rows and pagination is displaying only 10 rows. If you update some rows and press navigation button (Next/Previous) the changes you have made are lost and not saved. I also have a workaround for this if you are interested please let me know. I will post you if you need it.

HTTP 400 Bad Request Error

Application Express 3.1.1.00.09
We have some users who are experiencing what appears to be a browser problem in one of our APEX applications.
When clicking on any button that does an insert or update to the database some users get an HTTP-400 Bad Request error message. The database does not get updated and anything they click on after that shows that message. In most cases we have been able to restore the user’s browser to the default settings and the issue is resolved. However, we were not able to isolate which browser setting is causing the issue. We have seen the issue in IE 6, IE 7 and IE 8.
Here’s the error we see in the Apache server error log (minus the date time stamp and IP addresses):
mod_plsql: /pls/ax_tastest/wwv_flow.accept HTTP-400 Invalid name
Does anyone else have a solution for this? Know what's causing it?

HTTP 400 Bad Request Error from APEX 3.1.1.00.09.
We were able to determine that only PCs which had the Google toolbar installed were getting the HTTP 400 Bad Request Error from a particular page in one of our applications. Further testing revealed that turning off the ‘auto-fill’ feature of the Google toolbar would prevent the error from occurring and the application would behave normally. We were able to identify a specific item on the page that was the root cause. The item was using the type “Text area with HTML Editor” which has been deprecated. We changed the page item type to “HTML editor standard” and this has resolved the issue with or without the Google Toolbar and auto-fill feature enabled.
Summary:
•     Browser setting: Google toolbar enabled with auto-fill enabled.
Apex page item of type: ‘Text area with HTML Editor’.
When a user clicks on a button in the page, that executes a page process, it results in HTTP 400 error.
•     Browser setting: Google toolbar enabled with auto-fill disabled.
Apex page item of type: ‘Text area with HTML Editor’.
When a user clicks on a button in the page, everything goes through correctly and there is no error.
•     Browser setting: Google toolbar enabled with auto-fill disabled or enabled.
Apex page item of type: ‘HTML Editor Standard’.
When a user clicks on a button in the page, everything goes through correctly and there is no error.

INVITE with display-name="" in Contact header- 400 Bad request from occas

Hi,
When a UAC sends an INVITE to OCCAS
with the Contact header in the form :
Contact: "" <sip:user@domain>
OCCAS rejects the message with 400 Bad request.
The problem comes from display-name = ""
(proven easily with sipp)
In the 400 response : X-Bad-Request: Illegal header "Contact"
It seems that the string "" as display name should be allowed according to rfc 3261:
display-name = *(token LWS)/ quoted-string
quoted-string = SWS DQUOTE *(qdtext / quoted-pair ) DQUOTE
qdtext = LWS / %x21 / %x23-5B / %x5D-7E/ UTF8-NONASCII
quoted-pair = "\" (%x00-09 / %x0B-0C / %x0E-7F)
Has anyone encountered the problem?
regards
Christophe

Hi LJ, you may want to post over on the new My Oracle Support Communications Community which is moderated by and responded to by Oracle Support and accessible by Oracle customers. Many new features will be developed for the Community in the coming months, please come and check it out at https://metalink.oracle.com/CSP/ui/index.html
Regards
Graham

Apache as reverse proxy - 400 Bad request

Hi all,
I'm configured apache as reverse proxy according to this blog:
The Reverse Proxy Series -- Part 3: Apache as a reverse-proxy
When I try to navigate http://testcomp/irj I get "400 - Bad request"
See exception;
Message : User Guest, IP address
Cannot parse the http request. Http error response [400 Bad Request] will be returned. Request is [Host: sapportal:50000
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, /
Accept-Language: en,he;q=0.5
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; FDM; .NET CLR 2.0.50727)
Max-Forwards: 10
Via: 1.1 localhost
X-Forwarded-For: 10.0.0.4
X-Forwarded-Host: 10.0.0.6
X-Forwarded-Server: localhost
Connection: Keep-Alive
GET /irj HTTP/1.1
Host: sapportal:50000
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, /
Accept-Language: en,he;q=0.5
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322; FDM; .NET CLR 2.0.50727)
Max-Forwards: 10
Via: 1.1 localhost
X-Forwarded-For: 10.0.0.4
X-Forwarded-Host: 10.0.0.6
X-Forwarded-Server: localhost
Connection: Keep-Alive
com.sap.engine.services.httpserver.exceptions.HttpIllegalArgumentException: Incompatible field content in the MIME header.
 at com.sap.engine.services.httpserver.lib.headers.MimeHeaderField.parse(MimeHeaderField.java:364)
 at com.sap.engine.services.httpserver.lib.headers.MimeHeaders.init(MimeHeaders.java:504)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.initialize(RequestAnalizer.java:196)
 at com.sap.engine.services.httpserver.server.Client.initialize(Client.java:84)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:143)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Severity : Error
Category :
Location : com.sap.engine.services.httpserver
Application :
Thread : SAPEngine_Application_Thread[impl:3]_32
Datasource : 9332850:C:usrsapPD9JC00j2eeclusterserver0logdefaultTrace.trc
Message ID : 000C29EFE9A300570000002D00000B9000043A81D3311894
Source Name : com.sap.engine.services.httpserver
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : 5359e85066e411dcbf6b000c29efe9a3
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives :
Resource Bundlename :
Session : 2
Source : com.sap.engine.services.httpserver
ThreadObject : SAPEngine_Application_Thread[impl:3]_32
Transaction :
User : Guest
The lines I added to http.conf
#Enable reverse-proxying
ProxyVia on
ProxyTimeout 600
#disable forward-proxying
ProxyRequests Off
#proxy /irj both ways
ProxyPass /irj http://sapportal:50000/irj
ProxyPassReverse /irj http://testcomp/irj
#proxy /logon both ways
ProxyPass /logon http://sapportal:50000/logon
ProxyPassReverse /logon http://testcomp/logon
I tried with apache version 2.2.3 & 2.0.59 with no success.
My J2EE/Portal version is 6.17.
Since this is a testing environment the two computers are under the same workgroup (no domain).
If I naviagte directly to the portal (without the reverse proxy) everything is working.
How can I solve it?
Regards,
Omri

Hi Jakub,
Thanks for the answer.
It's not working for me...
I'm attaching my httpd.conf file.
Also, what apache version do you use?
Can you send me your post your httpd.conf file?
Thanks,
Omri
httpd.conf
This is the main Apache HTTP server configuration file. It contains the
configuration directives that give the server its instructions.
See <URL:http://httpd.apache.org/docs/2.2/> for detailed information.
In particular, see
<URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
for a discussion of each configuration directive.
Do NOT simply read the instructions in here without understanding
what they do. They're here only as hints or reminders. If you are unsure
consult the online docs. You have been warned.
Configuration and logfile names: If the filenames you specify for many
of the server's control files begin with "/" (or "drive:/" for Win32), the
server will use that explicit path. If the filenames do not begin
with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
with ServerRoot set to "c:/apache" will be interpreted by the
server as "c:/apache/logs/foo.log".
NOTE: Where filenames are specified, you must use forward slashes
instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
If a drive letter is omitted, the drive on which Apache.exe is located
will be used by default. It is recommended that you always supply
an explicit drive letter in absolute paths, however, to avoid
confusion.
ThreadsPerChild: constant number of worker threads in the server process
MaxRequestsPerChild: maximum number of requests a server process serves
ThreadsPerChild 250
MaxRequestsPerChild 0
ServerRoot: The top of the directory tree under which the server's
configuration, error, and log files are kept.
Do not add a slash at the end of the directory path. If you point
ServerRoot at a non-local disk, be sure to point the LockFile directive
at a local disk. If you wish to share the same ServerRoot for multiple
httpd daemons, you will need to change at least LockFile and PidFile.
ServerRoot "c:/apache"
Listen: Allows you to bind Apache to specific IP addresses and/or
ports, instead of the default. See also the <VirtualHost>
directive.
Change this to Listen on specific IP addresses as shown below to
prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#Listen 12.34.56.78:80
Listen 80
Dynamic Shared Object (DSO) Support
To be able to use the functionality of a module which was built as a DSO you
have to place corresponding `LoadModule' lines at this location so the
directives contained in it are actually available before they are used.
Statically compiled modules (those listed by `httpd -l') do not need
to be loaded here.
Example:
LoadModule foo_module modules/mod_foo.so
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule headers_module modules/mod_headers.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule status_module modules/mod_status.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
#LoadModule ssl_module modules/mod_ssl.so
'Main' server configuration
The directives in this section set up the values used by the 'main'
server, which responds to any requests that aren't handled by a
<VirtualHost> definition. These values also provide defaults for
any <VirtualHost> containers you may define later in the file.
All of these directives may appear inside <VirtualHost> containers,
in which case these default settings will be overridden for the
virtual host being defined.
ServerAdmin: Your address, where problems with the server should be
e-mailed. This address appears on some server-generated pages, such
as error documents. e.g. [email protected]
ServerAdmin @@ServerAdmin@@
ServerName gives the name and port that the server uses to identify itself.
This can often be determined automatically, but we recommend you specify
it explicitly to prevent problems during startup.
If your host doesn't have a registered DNS name, enter its IP address here.
ServerName localhost:80
DocumentRoot: The directory out of which you will serve your
documents. By default, all requests are taken from this directory, but
symbolic links and aliases may be used to point to other locations.
DocumentRoot "c:/apache/htdocs"
Each directory to which Apache has access can be configured with respect
to which services and features are allowed and/or disabled in that
directory (and its subdirectories).
First, we configure the "default" to be a very restrictive set of
features.
<Directory />
 Options FollowSymLinks
 AllowOverride None
 Order deny,allow
 Deny from all
 Satisfy all
</Directory>
Note that from this point forward you must specifically allow
particular features to be enabled - so if something's not working as
you might expect, make sure that you have specifically enabled it
below.
This should be changed to whatever you set DocumentRoot to.
<Directory "c:/apache/htdocs">
Possible values for the Options directive are "None", "All",
or any combination of:
Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
Note that "MultiViews" must be named explicitly --- "Options All"
doesn't give it to you.
The Options directive is both complicated and important. Please see
http://httpd.apache.org/docs/2.2/mod/core.html#options
for more information.
 Options Indexes FollowSymLinks
AllowOverride controls what directives may be placed in .htaccess files.
It can be "All", "None", or any combination of the keywords:
Options FileInfo AuthConfig Limit
 AllowOverride None
Controls who can get stuff from this server.
 Order allow,deny
 Allow from all
</Directory>
DirectoryIndex: sets the file that Apache will serve if a directory
is requested.
<IfModule dir_module>
 DirectoryIndex index.html
</IfModule>
The following lines prevent .htaccess and .htpasswd files from being
viewed by Web clients.
<FilesMatch "^\.ht">
 Order allow,deny
 Deny from all
</FilesMatch>
ErrorLog: The location of the error log file.
If you do not specify an ErrorLog directive within a <VirtualHost>
container, error messages relating to that virtual host will be
logged here. If you do define an error logfile for a <VirtualHost>
container, that host's errors will be logged there and not here.
ErrorLog logs/error.log
LogLevel: Control the number of messages logged to the error_log.
Possible values include: debug, info, notice, warn, error, crit,
alert, emerg.
LogLevel warn
<IfModule log_config_module>
The following directives define some format nicknames for use with
a CustomLog directive (see below).
 LogFormat "%h %l %u %t \"%r\" %>s %b \"%You need to enable mod_logio.c to use %I and %Oi\" \"%{User-Agent}i\"" combined
 LogFormat "%h %l %u %t \"%r\" %>s %b" common
 <IfModule logio_module>
 LogFormat "%h %l %u %t \"%r\" %>s %b \"%i\" \"%{User-Agent}i\" %I %O" combinedio
 </IfModule>
The location and format of the access logfile (Common Logfile Format).
If you do not define any access logfiles within a <VirtualHost>
container, they will be logged here. Contrariwise, if you do
define per-<VirtualHost> access logfiles, transactions will be
logged therein and not in this file.
 CustomLog logs/access.log common
If you prefer a logfile with access, agent, and referer information
(Combined Logfile Format) you can use the following directive.
 #CustomLog logs/access.log combined
</IfModule>
<IfModule alias_module>
Redirect: Allows you to tell clients about documents that used to
exist in your server's namespace, but do not anymore. The client
will make a new request for the document at its new location.
Example:
Redirect permanent /foo http://www.example.com/bar
Alias: Maps web paths into filesystem paths and is used to
access content that does not live under the DocumentRoot.
Example:
Alias /webpath /full/filesystem/path
If you include a trailing / on /webpath then the server will
require it to be present in the URL. You will also likely
need to provide a <Directory> section to allow access to
the filesystem path.
ScriptAlias: This controls which directories contain server scripts.
ScriptAliases are essentially the same as Aliases, except that
documents in the target directory are treated as applications and
run by the server when requested rather than as documents sent to the
client. The same rules about trailing "/" apply to ScriptAlias
directives as to Alias.
 ScriptAlias /cgi-bin/ "c:/apache/cgi-bin/"
</IfModule>
"c:/apache/cgi-bin" should be changed to whatever your ScriptAliased
CGI directory exists, if you have that configured.
<Directory "c:/apache/cgi-bin">
 AllowOverride None
 Options None
 Order allow,deny
 Allow from all
</Directory>
Apache parses all CGI scripts for the shebang line by default.
This comment line, the first line of the script, consists of the symbols
pound (#) and exclamation followed by the path of the program that
can execute this specific script. For a perl script, with perl.exe in
the C:\Program Files\Perl directory, the shebang line should be:
 #!c:/program files/perl/perl
Note you mustnot_ indent the actual shebang line, and it must be the
first line of the file. Of course, CGI processing must be enabled by
the appropriate ScriptAlias or Options ExecCGI directives for the files
or directory in question.
However, Apache on Windows allows either the Unix behavior above, or can
use the Registry to match files by extention. The command to execute
a file of this type is retrieved from the registry by the same method as
the Windows Explorer would use to handle double-clicking on a file.
These script actions can be configured from the Windows Explorer View menu,
'Folder Options', and reviewing the 'File Types' tab. Clicking the Edit
button allows you to modify the Actions, of which Apache 1.3 attempts to
perform the 'Open' Action, and failing that it will try the shebang line.
This behavior is subject to change in Apache release 2.0.
Each mechanism has it's own specific security weaknesses, from the means
to run a program you didn't intend the website owner to invoke, and the
best method is a matter of great debate.
To enable the this Windows specific behavior (and therefore -disable- the
equivilant Unix behavior), uncomment the following directive:
#ScriptInterpreterSource registry
The directive above can be placed in individual <Directory> blocks or the
.htaccess file, with either the 'registry' (Windows behavior) or 'script'
(Unix behavior) option, and will override this server default option.
DefaultType: the default MIME type the server will use for a document
if it cannot otherwise determine one, such as from filename extensions.
If your server contains mostly text or HTML documents, "text/plain" is
a good value. If most of your content is binary, such as applications
or images, you may want to use "application/octet-stream" instead to
keep browsers from trying to display binary files as though they are
text.
DefaultType text/plain
<IfModule mime_module>
TypesConfig points to the file containing the list of mappings from
filename extension to MIME-type.
 TypesConfig conf/mime.types
AddType allows you to add to or override the MIME configuration
file specified in TypesConfig for specific file types.
 #AddType application/x-gzip .tgz
AddEncoding allows you to have certain browsers uncompress
information on the fly. Note: Not all browsers support this.
 #AddEncoding x-compress .Z
 #AddEncoding x-gzip .gz .tgz
If the AddEncoding directives above are commented-out, then you
probably should define those extensions to indicate media types:
 AddType application/x-compress .Z
 AddType application/x-gzip .gz .tgz
AddHandler allows you to map certain file extensions to "handlers":
actions unrelated to filetype. These can be either built into the server
or added with the Action directive (see below)
To use CGI scripts outside of ScriptAliased directories:
(You will also need to add "ExecCGI" to the "Options" directive.)
 #AddHandler cgi-script .cgi
For type maps (negotiated resources):
 #AddHandler type-map var
Filters allow you to process content before it is sent to the client.
To parse .shtml files for server-side includes (SSI):
(You will also need to add "Includes" to the "Options" directive.)
 #AddType text/html .shtml
 #AddOutputFilter INCLUDES .shtml
</IfModule>
The mod_mime_magic module allows the server to use various hints from the
contents of the file itself to determine its type. The MIMEMagicFile
directive tells the module where the hint definitions are located.
#MIMEMagicFile conf/magic
Customizable error responses come in three flavors:
1) plain text 2) local redirects 3) external redirects
Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
EnableMMAP and EnableSendfile: On systems that support it,
memory-mapping or the sendfile syscall is used to deliver
files. This usually improves server performance, but must
be turned off when serving from networked-mounted
filesystems or if support for these functions is otherwise
broken on your system.
#EnableMMAP off
#EnableSendfile off
Supplemental configuration
The configuration files in the conf/extra/ directory can be
included to add extra features or to modify the default configuration of
the server, or you may simply copy their contents here and change as
necessary.
Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf
Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf
Fancy directory listings
#Include conf/extra/httpd-autoindex.conf
Language settings
#Include conf/extra/httpd-languages.conf
User home directories
#Include conf/extra/httpd-userdir.conf
Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf
Virtual hosts
#Include conf/extra/httpd-vhosts.conf
Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf
Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf
Various default settings
#Include conf/extra/httpd-default.conf
Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
Note: The following must must be present to support
 starting without SSL on platforms with no /dev/random equivalent
 but a statically compiled-in mod_ssl.
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
ProxyPreserveHost On
ProxyVia on
ProxyTimeout 600
#disable forward-proxying
ProxyRequests Off
#proxy /irj both ways
ProxyPass /irj http://sapportal:50000/irj
ProxyPassReverse /irj http://sapportal:50000/irj
#ProxyPassReverse /irj http://testcomp/irj
#proxy /logon both ways
ProxyPass /logon http://sapportal:50000/logon
ProxyPassReverse /logon http://sapportal:50000/logon
#ProxyPassReverse /logon http://testcomp/logon

Getting "HTTP 400 Bad Request" error when submitting form

I am using APEX 3.1.2. I have a form based on a table. The form contains check boxes, a multiple select item, some text items and some text boxes with HTML editors. It had been working properly but now is giving me the dreaded "The web page can not be found..." error page as soon as I click create when in create mode or the update or the delete button when editing a row of data. The URL in the address area of the browser is: "http://ndhoast.tsh.mis.mckesson.com:7778/pls/apex/wwv_flow.accept" and the tab says "HTTP 400 Bad Request".
Any help would be greatly appreciated!

Do you have any extra Javascript components added in? We've been doing work with ExtJS and Oracle Apex, and I've noticed that on one particular page there is a bad request thrown when a doSubmit() is called. When the Javascript is commented out, the page works fine.

HTTP 400 - Bad request Page cannot be found while submitting tabular form

Hi,
My Apex application has sql report for summary and tabular form in a single page.
This page is working fine when the number of rows per screen is upto 130.
When we sets the maximum number of rows as more than 130, it displays the record but if we click button to submit the page to save
it shows page cannot be found.
HTTP 400 - Bad request
URL shows apex URL followed by /wwv_flow.accept
Is there any maximum limits to show number of records in a page in apex.
Since number of rows selection is not there in tabular form I created a select list with submit item with values 10,20,50,100,500,1000.
default value is '15'.
My tabular form has 15 columns and out of them 12 are editable.
Apex version is 3.1.

Sounds like you're submitting too many parameters (15 * 130 = 1950), very close to 2000
Check this post our regarding PlsqlMaxParameters
"Page cannot be found" error when submitting tabular form
Scott

HTTP 400 Bad Request error in master/detail report

Using APEX 3.2
I have master/detail report and thought all was working fine because the detail lines were less than 100. I increased the number of lines to 300 and then when the Save or Delete buttons are pressed, we get the HTTP 400 Bad Request error. I decreased the lines to 100 (about 32K) and everything works again.
Is there a size limitation on the detail? FYI - the header regeion is on the same page as the detail. If there is a size limitation, is there a way to increase this?
If you experts don't think the error is a result of the size, could there be another cause?
THANKS FOR YOUR HELP!
Sandie

Hi All,
Issue resolved:) ...that due to When calling a URL in the REST Receiver Channel, all GET variables are ignored
so we had to upgrade SP10 patch level 5 and all services are working as we expected.
Also pls check Note :2114322
Thanks,
Maheswarareddy

Content-Type is net being set in HTTP header. Server returns 400 Bad Request error.

Hi,
I am trying to access an XML WebService. This service requires the content type of the request to be set to "text/xml". As you can see in the source code, I am setting the req.ContentType property to "text/xml".
However, this content type seems not to be added to the HTTP headers. The server returns a 400 Bad Request error as can be seen in the log.
I've attached a System.Net.trace log and it states:
[Public Key]
Algorithm: RSA
Length: 2048
Key Blob: 30 82 01 0a 02 82 01 01 00 bc 09 30 8a 1e 03 4d 7a ea 16 d3 a8 5e d8 5b 00 c4 8a c5 9f 26 bd 7d d6 cb 8b d0 db bd 93 2d 2b 3b 84 f6 20 79 83 34 67 51 37 21 ea 56 5e 18 d8 a3 db 72 43 0e 14 77 e2 64 cb 07 b6 2a 81 c7 f5 16 dd 19 c7 d9 68 0b 3a 81 5c f0 05 c9 ed 2b 37 00 31 41 37 8b 3a 73 4a 4d ab d7 d8 87 79 35 82 01 97 e3 3c be bb 84 e5 94 bb 87 52 e3 9f b5 fb 3e 33 38 c3 eb 73 42 ee ba 1e c5 4a 33 18 a1 0d 8a d2 10 a8 c5 3....
System.Net Information: 0 : [26780] SecureChannel#31884011 - Remote certificate was verified as valid by the user.
System.Net Information: 0 : [26780] ConnectStream#26966483 - Sending headers
API-VERSION: 1
Host: test.myhost.com
Content-Length: 329
Expect: 100-continue
Connection: Keep-Alive
System.Net Information: 0 : [26780] Connection#3888474 - Received status line: Version=1.1, StatusCode=100, StatusDescription=Continue.
System.Net Information: 0 : [26780] Connection#3888474 - Received headers
System.Net Information: 0 : [26780] Connection#3888474 - Received status line: Version=1.1, StatusCode=400, StatusDescription=Bad Request.
System.Net Information: 0 : [26780] Connection#3888474 - Received headers
0: Content-type
1: text/xml
X-Debug-Token: a810dc
X-Debug-Token-Link: /service/_profiler/a810dc
Connection: keep-alive
Content-Length: 3440
Cache-Control: no-cache
Content-Type: text/html; charset=UTF-8
Date: Tue, 14 Apr 2015 11:07:11 GMT
Server: Apache
...and here's the implementation of the web request:
private void ButtonSend_Click(object sender, EventArgs e)
WebHeaderCollection whCol = new WebHeaderCollection();
whCol.Add("API-VERSION", "1");
//whCol.Add("Content-Type", "text/xml; charset=UTF-8"); <-- That doesn't work in .NET. Content-Type has to be set on the ContentType-Property
string msg = _textBoxReq.Text;
HttpWebRequest req = (HttpWebRequest)WebRequest.Create(_textBoxURL.Text);
byte[] data = Encoding.UTF8.GetBytes(msg);
req.Method = "POST";
req.ContentType = "text/xml; charset=UTF-8";
req.ContentLength = data.Length;
req.Headers = whCol;
req.GetRequestStream().Write(data, 0, data.Length);
string xml = "";
try
using (HttpWebResponse resp = (HttpWebResponse)req.GetResponse())
using (System.IO.StreamReader sr = new System.IO.StreamReader(resp.GetResponseStream()))
xml = sr.ReadToEnd().Trim();
catch (WebException we)
using (System.IO.StreamReader sr = new System.IO.StreamReader(we.Response.GetResponseStream()))
xml = sr.ReadToEnd().Trim();
_textBoxRes.Text = xml;
Can anyone help?
Thanks,
MiRi

Hi _MiRichter,
Well Done!
Thank you very much for sharing the solution to us.
Best Regards,
Amy Peng
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request

Hi,
We are doing File to WCF Scenario( SOAP ). I am trying to post the Data to WCf usingf SOAP Reciver Adapter.
Getting the Following error.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request
Thanks in advance

>>> Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 400 Bad Request
Answer: Use the third party wsdl in SOAP UI or any soap client tool and send the request and see the response. The problem here is the message structure mismatch between your request to the webservice and webservice expecting...
Possible 2 reasons:
1) You are not creating the target message based on the wsdl structure or not configured soap receiver properly.
or
2 ) Your wsdl is not latest or updated one or some changes have happened in the third party webservice hosting side.

BC Sender Adapter--400 Bad Request

Hi,
I am trying to integrate BC with XI(BC Sender Adapter). BC will send Data to XI.
In BC, i have specified a routing rule( as specified in help.sap.com) using the following parameters :
URL:http://<hostname:portnumber>/MessagingSystem/receive/BcAdapter/BC
User:xiappluser
When i test this service, it gives the error 400 Bad Request. I tested the validitly of the above URL by loggin in through a web-browser. The messaging servlet is seen in active status.
<?xml version="1.0" encoding="UTF-8" ?>
- <scenario>
<scenname>MSG_SCEN</scenname>
<scentype>SERV</scentype>
<sceninst>MSG_001</sceninst>
<scenversion>001</scenversion>
- <component>
<compname>SERVLET</compname>
<compdesc>Messaging System</compdesc>
<comphost>localhost</comphost>
<compinst>MSG_001</compinst>
- <message>
<messalert>OKAY</messalert>
<messseverity>100</messseverity>
<messarea>QR</messarea>
<messnumber>801</messnumber>
<messparameter>na</messparameter>
<messtext>MessagingServlet is active.</messtext>
</message>
</component>
</scenario>
Even when i test the URL http://<hostname>:50000 from BC,the response code is 200(success). But the problem is when i try to post the request to messaging servlet (400 bad request).
Can some body suggest me how to go about.
Regards,
Siva Maranani.

hi,
I was able to get the error details of "400:Bad Request."
The error is :
com.sap.aii.af.ra.ms.api.MessageFormatException: got no name/namespace for the payload of the XRFC_DOC_TYPE_ENVELOPE.
org.xml.sax.SAXexception:got no name/namespace for the payload of the XRFC_DOC_TYPE_ENVELOPE.
Below is the xmldata, that i am sent to XI:
<?xml version="1.0" encoding="iso-8859-1"?>
<sap:Envelope xmlns:sap="urn:sap-com:document:sap" version="1.0">
<sap:Header xmlns:rfcprop="urn:sap-com:document:sap:rfc:properties">
 <saptr:From xmlns:saptr="urn:sap-com:document:sap:transport">BC</saptr:From>
 <saptr:To xmlns:saptr="urn:sap-com:document:sap:transport">XI</saptr:To>
</sap:Header>
<sap:Body>
 <rfc:ZSIVAINSERT xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
 <CARRID>AA<CARRID>
 <CONNID>0017<CONNID/>
 <FLDATE>20040417<FLDATE/>
 </rfc:ZSIVAINSERT>
</sap:Body>
</sap:Envelope>
I do not understand the name/namespace it is looking for. Kindly help me out.
Regards,
Siva Maranani

HTTP/1.1 400 Bad Request error in receiver REST channel

Hi Experts
I am currently working on an interface in which we have created a REST communication channel on the receiver side.
The below error comes up in the PI when we try to perform the GET operation on the URLs given below:
Error Message: HTTP error occurred: HTTP/1.1 400 Bad Request
URLs -
i) https://<myHost>:<myPort>/businesses/search?Keyword=Viridor&ResultsPerPage=10
ii) https://<myHost>:<myPort>/businesses/ec92a1e9-cef0-48aa-8800-a2e500ce8b1c/sites?Keyword=Viridor&ResultsPerPage=10
When we use SOAP UI to perform the above test, it works perfectly fine and fetches the required response from the target REST server.
Also, when we use the URL - https://<myHost>:<myPort>/businesses in the receiver communication channel in PI, it works fine and retrieves the
values of all the businesses present on the target server, however on making URL more specific - like the two URLs above, it does not work
and gives the bad request message.
Please can you let me know what could be the issue.
Thanks,
Maheswarareddy

Hi All,
Issue resolved:) ...that due to When calling a URL in the REST Receiver Channel, all GET variables are ignored
so we had to upgrade SP10 patch level 5 and all services are working as we expected.
Also pls check Note :2114322
Thanks,
Maheswarareddy

Apex no respond 400 bad request

Similar Messages

Maybe you are looking for