Mod_plsql: /pls/orasso/ORASSO.wwsso_app_admin.fapp_process_login HTTP-400

Hi,
i write role in httpd.conf, to redirect to an external application, as this:
ProxyPass /pippo/ http://<myhost>:7777/pls/orasso/ORASSO.wwsso_app_admin.fapp_process_login?p_app_id=DF435C2A789ACE9C183480A1A6A982CD
ProxyPassReverse /pippo/ http://<myhost>:7777/pls/orasso/ORASSO.wwsso_app_admin.fapp_process_login?p_app_id=DF435C2A789ACE9C183480A1A6A982CD
bun when i try to access at <myhost>/pippo/ i receive the follow http error:
mod_plsql: /pls/orasso/ORASSO.wwsso_app_admin.fapp_process_login
HTTP-400 Name "ORASSO.wwsso_app_admin.fapp_process_login?p_app_id=DF435C2A789ACE9C183480A1A6A982CD" is longer than 30 chars
Is this a problem of mod_plsql or an Apache (Proxypass)?
Are somebody resolve it?
Thanks a lot to all!!!
Stefano

Yes Frank, I'm using DAS.
I found the problem, There was a previous SSO server installation and It was causing a conflict.
Now I have fixed the error running SSOREG script, the problem now is when accessing with a valid user the Apache.exe dies. The OID seems to be working fine since any wrong user is rejected, but when valid user the apache dies.
I'm looking for information about this error.
Any Idea?

Similar Messages

  • HTTP 400 Error during logoff

    Hi all!
    I have menu Portlet, which just contains URL links. This menu also contains logout URL:
    http://mineserv:port/pls/orasso/orasso.wwsso_app_admin.ls_logout?p_done_url=<logout URL>
    It works most part of time, but sometimes I have error 404:
    The requested URL /pls/orasso/orasso.wwsso_app_admin.ls_logout was not found on this server.
    I don't understand what happens...Can anybody explain me what problem I have. May be I do something wrong...I don't know.
    Thanks and excuse me for my English
    Message was edited by:
    kostik

    In HTTP Server error log I found such message:
    mod_plsql: /pls/portal/PORTAL.wwsec_app_priv.logout HTTP-404 PORTAL.wwsec_app_priv.logout: SIGNATURE (parameter names) MISMATCH VARIABLES IN FORM NOT IN PROCEDURE: P_DONE_URL NON-DEFAULT VARIABLES IN PROCEDURE NOT IN FORM:

  • Mod_plsql: /pls/apex/wwv_flow.accept HTTP-400 Too many arguments passed in.

    Hi All ,
    I want one solution i have a report which fectches the ppt that r stored in db,If i search more results it errors out so i have reduced the results and it was working fine.Now i see it is giving the same error(as below) althorugh it was working fine by reducing results in query.Can anybody please help me in this.
    the error is
    Bad Request
    Your browser sent a request that this server could not understand.
    mod_plsql: /pls/apex/wwv_flow.accept HTTP-400 Too many arguments passed in. Got 3250 parameters. Upper limit is 2000
    Oracle-Application-Server-10g/10.1.3.1.0 Oracle-HTTP-Server Server at insightapps.oraclecorp.com Port 80

    Section 1.10 of the Oracle HTTP Server mod_plsql User's Guide states the following
    The total number of name value pairs that can be passed to a PL/SQL procedure is 2000.
    mod_plsql limits the total number of parameters that can be passed to a single procedure to 2000.
    mod_plsql limits the size of a single parameter that can be passed to a procedure to 32000 bytes.
    It would be helpful to know how each of these apply in the APEX context
    Varad

  • Mod_plsql: /pls/apex/f HTTP-400 Missing '=' in query string or post form

    This is the message when I click the logout button. It destroys the session though. It should redirect to login page after clicking logout button.
    We are on Apex 4.1
    Bad Request
    Your browser sent a request that this server could not understand.
    mod_plsql: /pls/apex/f HTTP-400 Missing '=' in query string or post form
    Oracle-Application-Server-10g/10.1.2.2.0 Oracle-HTTP-Server Server at xxxx.xxxxx.edu Port 443
    Edited by: 965704 on Oct 30, 2012 11:42 AM

    It has been fixed but the new problem is: After signout, if I move back to previous page and click some link using <- sign then I suppose to get the login page, but i am getting
         ORA-44004: invalid qualified SQL name error message.
    The source for my login page is
    wwv_flow_custom_auth_std.login(
    P_UNAME => :P101_USERNAME,
    P_PASSWORD => :P101_PASSWORD,
    P_SESSION_ID => v('APP_SESSION'),
    P_FLOW_PAGE => :APP_ID||':1'
    );

  • Mod_plsql: /pls/apex/f  SSO on 11g (11.1) ,iAS 10.1.2.0.2 , Apex 3.1.2 bug?

    Hello,
    I just configured SSO on our first 11G database exactly the same way as our 9i databases( Yes we skip 10)
    But I don't seem to get it running.
    Environment: Apex 3.1.2 on RDBMS 11.1
    Windows server 20003 standard
    iAS : 10.1.2.0.2
    I configured and installed SSO on the DB and registered with the ORASSO
    When I login to the dev environment using:
    http://w3gvb772.glaverbel.com:7778/pls/apex_dev11gut/
    It works fine because SSO is not used
    But when I go immediately to the SSO enabled application using
    http://w3gvb772.glaverbel.com:7778/pls/apex_dev11gut/f?p=1001:1
    I do not get redirected to the SSO login page but instead the URL is rewritten to
    http://w3gvb772.glaverbel.com:7778/pls/apex_dev11gut/f
    Giving the following error on IE7
    Expecting p_company or wwv_flow_company cookie to contain security group id of application owner.
    Error ERR-7620 Could not determine workspace for application ().
    OK
    And in firefox
    Bad Request
    Your browser sent a request that this server could not understand.
    mod_plsql: /pls/apex_dev11gut/f HTTP-400 Bad parameter name: none specified
    Has someone encountered this problem?
    I saw there was a problem that /pls/apex was rewritten as /plsapex/ but this is NOT the case here.
    Thanks
    Erwin
    Edited by: Erwin L on Feb 26, 2009 9:30 AM

    Hi Scott,
    Thiese are the last 5 lines from thje apache error log
    [Wed Mar 04 08:34:17 2009] [error] [client 193.202.68.83] [ecid: 3061116036902,1] (10054)An existing connection was forcibly closed by the remote host: MOD_OC4J_0087: Got an unexpected error while calling send() to send a message to oc4j and the error code is 10054.
    [Wed Mar 04 08:34:17 2009] [error] [client 193.202.68.83] [ecid: 3061116036902,1] MOD_OC4J_0053: Failed to call network routine to send out an ajp13 buffer message to oc4j.
    [Wed Mar 04 08:34:17 2009] [warn] [client 193.202.68.83] [ecid: 3061116036902,1] MOD_OC4J_0027: Failed to send out an ajp13 message to oc4j.
    [Wed Mar 04 08:34:17 2009] [error] [client 193.202.68.83] [ecid: 3061116036902,1] MOD_OC4J_0026: Failed to marshal a request to ajp13 message headers or send them to the web container.
    [Wed Mar 04 08:39:35 2009] [error] [client 10.132.130.29] [ecid: 1236152375:193.202.68.83:2284:2504:2,0] File does not exist: d:/oracle/server10.1.2.2/apache/apache/htdocs/pls/apex/wwv_flow_custom_auth_sso.process_success
    These are the last lines from the apache acceslog file
    10.132.130.29 - APEX_PUBLIC_USER [04/Mar/2009:08:39:35 +0100] "GET /pls/apex_dev11gut/f?p=1001:1 HTTP/1.1" 200 878
    10.132.130.29 - - [04/Mar/2009:08:39:35 +0100] "GET /pls/apex/wwv_flow_custom_auth_sso.process_success?urlc=v1.2~E274EB9F5E9877B824734621A287A2DD42394F7973CF4593FD816F085275EF57D4DCDFF2A11DC7854955A946E9B82D45E46A68F2755C1093B9BBC221A42CF2C26A28745E66B9F55D04C021E312EBC0D29E9974F8028679F1AAA320BB876524A3BC03148CBB44A69BC459770BBA6015DD911D5515739850EF8690AF43FC4380F2CBF7B35A27D97B51BBAB2A753FF24AD426802A6BDE6F14203FE2AEDD7BD8F2EB68C441BCF5766259C56C721070FC8C3453FA1E72EAE0802380AC2CE9919F00C04377425E06CB3048E936AD953CD74E677B3E27827F6799E3E8B8BDE6071D40F40409E98E35F2AD758D5D622459F0C00EE264BFA13508D13075B71C74EC1F3A8217758E1FBCC270CC884987B3AB8C3B52982DBB91DCA4C809C942C52844B10F713643D558BE31B0B4BD2615C70A60B4F4BF1ABD01FE49C347F71E4D220B547CC304DCE1572F6651F06A99E4A89081CE64261559CB8B352DC0DAF8EE0F8A887612CA679EE5FB86A2805DF22D9092A90D7CF37BEF5A190C3336E2842AF44FE2EC654D732573214D8C5B HTTP/1.1" 404 382
    193.202.68.83 - - [04/Mar/2009:08:39:52 +0100] "POST /reports/rwservlet/getserverinfo HTTP/1.1" 200 48
    193.202.68.83 - - [04/Mar/2009:08:40:10 +0100] "GET /forms/lservlet HTTP/1.1" 200 223
    193.202.68.83 - - [04/Mar/2009:08:41:10 +0100] "GET /forms/lservlet HTTP/1.1" 200 223
    193.202.68.83 - - [04/Mar/2009:08:41:19 +0100] "GET /reports/rwservlet/pingserver?server=W3GVB772RS01 HTTP/1.1" 200 3
    193.202.68.83 - - [04/Mar/2009:08:42:10 +0100] "GET /forms/lservlet HTTP/1.1" 200 223
    Erwin

  • 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.

  • 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 Too many arguments passed error

    I am getting the following error when using a multiselect list item to select/update data in the tabular form.
    Bad Request
    Your browser sent a request that this server could not understand.
    mod_plsql: /pls/otn/wwv_flow.accept HTTP-400 Too many arguments passed in. Got 2346 parameters. Upper limit is 2000
    Oracle-Application-Server-10g/10.1.2.3.0 Oracle-HTTP-Server Server at apex.oracle.com Port 80
    I have built this prototype application on the Oracle’s hosted apex.oracle.com site.
    The application page has three sections. Section 1 is an HTML region with the multiselect list. Section 2 is an HTML region with 20 text items. Section 3 has the tabular form with 25 columns that are used to update the data. The tabular form pagination values “Number of Row” and “Maximum Row Count” are set to 500.
    Up until now, the multiselect list in the Section 1 was just a simple select list and I never had any issues. I guess the number of arguments passed was low. Per our customer requirement, I had to change the simple select list to a multiselect list. Now, If I select multiple values in the select list, I get the above mentioned error. But, it does not seem to happen all the time. For example, the first time I select 3 values in the multiselect list, the page renders fine, and I am able to enter/save data in the tabular form. Then, I select two other values in the multiselect list, I would get the error.
    I am getting this error on the Oracle’s hosted apex.oracle.com site where my prototype application exists. And, according to the error oracle is using 10g/10.1.2.3.0. Is there any way to circumvent this issue so I can demo my application to the customer using the multiselect list?
    I found several threads on this forum regarding the same error and it seems that there was a bug in the older versions of Oracle Application server. Also, there were discussions about setting the PlsqlMaxParameters.
    Our dev/test/prod environment would be set up using the Oracle Application Server-10g/10.1.3. The question is would we need to add a line to set the PlsqlMaxParameters value in the plsql.conf file? In addition, what is the maximum value that it can be set to?
    Please forgive me for the longwinded description and the question - only way I could describe the situation.
    Thanks,
    DP

    Varad and Sc0tt,
    Thank you both for your responses.
    Varad – Yes, I can/will reduce the amount of data so it does not cause the tabular form to go over the 2000 field limit. If that is not possible, I will at least make the users aware of this issue. Since the same data is used for the other pages in the application, the users might want to keep all the data.
    Sc0tt – thanks for providing the information for your environment and settings. To plan for the future, we will have to set the value to something high also, around 8-10K range, and adjust later if we have to.
    Thank you both, I will mark both of your answers as helpful and the question as being answered.
    DP
    (Have either of you used the jquery datepicker solution? If yes, can you please take a look at my thread: Thread: Jquery Datepicker calendar problem with page scrolling
    Jquery Datepicker calendar problem with page scrolling

  • Apex Getting HTTP-400 error

    Hi,
    I created a form with many things to be updated and got this error. Can anyone help? Thanks.
    Bad Request
    Your browser sent a request that this server could not understand.
    mod_plsql: /pls/toolsdb/wwv_flow.accept HTTP-400 Too many arguments passed in. Got 2176 parameters. Upper limit is 2000

    Hello
    Can’t figure out what it causes but the solution is to schedule a little job with this statement:
    ALTER SYSTEM FLUSH SHARED_POOL
    Mortus...

  • Http-404   HTTP-400 Bad name in the request: not a legal PLSQ

    Hi All,
    I have apex 3.1.0.00.32 installed on solaris 10g R2. I didnt make any changes to a page which is based on report/query.
    When I modify the records I get the above error page not found HTTP 404
    When I check the apache logs I see
    mod_plsql: /pls/apex/src= HTTP-400 Bad name in the request: not a legal PLSQL identifer
    Any hints on this?
    thanks
    Rajesh

    Rajesh,
    When I modify the records
    Modify records how? Using what tool? What to you mean by "When"? Do you mean "after" modifying records you run the report and get the error or do you mean "in the process of" modifying records using a control in your application? What kind of report is this? Can you show us on apex.oracle.com?
    Scott

  • MODPLSQL-00370 HTTP-400 Illegal procedure name, has an empty part

    I currently have a 10g Orale HTTP server that runs fine.
    I am testing an install on a Linux box of the latest Oracle HTTP server but I am getting the above error everytime I try and access a pl/sql routine that runs fine on the 10g version.
    Server Version: Oracle-Application-Server-11g/11.1.1.2.0 Oracle-HTTP-Server (Unix) mod_ssl/11.0.0.0.0 OtherSSL/0.0.0 mod_plsql/11.1.1.0.0 mod_onsint/2.0
    Server Label: APACHE_11.1.1.2.0_LINUX.X64_091027.0947
    Server Built: Oct 28 2009 23:19:04
    I have created a basic pl/sql procedure called 'hello', granted access to public and created a public synonym
    On the 10g server it runs fine and displays hello world, on the 11g server it just gives the error :
    [2010-06-01T15:54:58.6856+01:00] [OHS] [ERROR:32] [OHS-9999] [mod_context.c] [host_id: web3.aspasia-mail.net] [host_addr: 127.0.0.1] [tid: 1168062784] [user: root] [ecid: 004Xz^cFbNZFw000jzwkno0002tc000002] [rid: 0] [VirtualHost: main] MODPLSQL-00370: mod_plsql: /pls/ashall/hello HTTP-400 Illegal procedure name, has an empty part
    There are no startup errors in the ohs log, the server serves static html pages fine, just an issue with the mod_plsql pages.
    OHS was installed as user oracle which was set up as per installation instructions
    any ideas???

    ok, I have got to the bottom of this and I have to say the error is totally rubbish!!
    The issuse is in the DAD file, even though on startup the dads.conf was parsed without an error!
    I have a default static html page if someone tries to go to the private DAD, ie
    PlsqlDefaultPage ../../authorisation.html
    Even though my call to the server is specifying the procedure I want for some reason the ../../ is causing the error ... if I remove the ../../, ie
    PlsqlDefaultPage authorisation.html
    and restart the ohs my hello page is returned fine!! So the error is actually relating to the ../../authorisation.html being an invalid procedure name despite the fact the ohs started without any errors at all!!

  • 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.

  • 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 Too many arguments passed

    Hello There,
    I installed the fresh 10g and applied patchset 2 on it. I get following error:
    HTTP-400 Too many arguments passed upper limit is 2000
    Please help

    Hello Qiang,
    Little more detail for your reference.
    README for 3355915
    MODPLSQL VERSION 9.0.2.6.0A ONE-OFF PATCH
    Date: January 6, 2004
    o What is in this patch?
    -> FIXES FOR:
    Bug#3355915 : BACKPORT BUG#3329645
    Bug#3116388 : TASK: MOD_PLSQL DOES NOT ALLOW PASSING MORE THAN 2000 PARAMETERS
    Bug#3024540 : NON-SUCCESS CODES WITH NO CONTENT SHOULD SERVE OHS ERRORDOCUMENT
    Bug#2023253 : NLS:FILE IS NOT PROPERTY UPLOADED IF IT'S FILENAME CONTAINS 0X5C
    Bug#3329645 : MODPLSQL IS UNABLE TO PASS PARAMETER LESS THAN 32K BYTES
    Bug#3264502 : DOC PATH REQUEST WITH PERPACKAGE AUTH CALL WRONG AUTH FUNCTION
    Bug#2802064 : ORA-01036 ILLEGAL VAR NAME/NUMBER USING VARIABLE NAMED P_ARRAY
    o What version can I apply this patch on?
    -> iAS 9.0.2.x.x

  • 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

Maybe you are looking for