HTTP error 403 to Integration engine

Hello,
Problem a)
While posing data from eSourcing to PI box by HTTP , we are getting HTTPerror 403.
The error message states:
ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL:
Problem b)
In another observation the sender file adapter after polling the file is unable to send the message to Integration engine and gives a Connection Time out error. it gives the following error.
Transmitting the message to endpoint http://<Host>:<Port>/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.net.ConnectException: Connection timed out: connect.
I believe that both the errors are for common cause and possibly the Integration engine is not accepting HTTP request.
Please help.
Thanks and Regards,
Himadri
Edited by: Himadri Chakraborty on Feb 9, 2010 3:35 PM

Time Out Error
In order to get rid of it, Your basis person need to play around with follwing three parameters in order to find an appropriate values as per your hardware sizing and requirement......
icm/conn_timeout
icm/keep_alive_timeout
icm/server_port_< n >
How ever, in general SAP recommandation is as follow....
icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=30,PROCTIMEOUT=600 to allow a maximum processing time of 10 minutes.
Hope this helps !!!
Regards,
J Augastine

Similar Messages

  • HTTP error 403 from Integration engine

    Hello,
    Problem a)
    While posing data from eSourcing to PI box by HTTP , we are getting HTTPerror 403.
    The error message states:
    ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL:
    Problem b)
    In another observation the sender file adapter after polling the file is unable to send the message to Integration engine and gives a Connection Time out error. it gives the following error.
    Transmitting the message to endpoint http://<Host>:<Port>/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.net.ConnectException: Connection timed out: connect.
    I believe that both the errors are for common cause and possibly the Integration engine is not accepting HTTP request.
    It looks like these error due to security reason, it seems some authorization profile is missing or may be some other issue,kindly help us at that front.
    Thanks and Regards,
    Satish

    Hi Suraj,
         Thanks for the update.We had checked the URL before posting this message,it is picking up correct URL with namespoace, UID and PWD.Exact error that we are getting is as follows:
    ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL: http://MB1ES1025:50200/sap/xi/adapter_plain?namespace=http://frictionless.esource.com/v2.0&interface=MI_ESI_AWARD_PO&service=FCI_TENANT&QOS=BE&sap-user=pisuper&sap-password=sap$29&sap-client=001&sap-language=EN. Please contact your system administrator.
    Here all information are correct.We have checked the SLD check, that is also working fine.Also it is not connectivity related issue, as we are able to transmit XML file to E-Sourcing.
       It looks like security issue, but what authorization needs tobe given exactly for HTTP call, we need to know or may be some other issue.
    Thanks and Regards,
    Satish

  • Getting HTTP Error 403 in Adaptor Engine Archival

    Hi,
    Getting below error
    Cannot read archived messages; reason: Reading Messages from Archive failed. Reason: java.lang.Exception: XML DAS SELECT command failed with ErrorCode: 403; ErrorText: <!DOCTYPE HTML PUBLIC
    I went through below blog but still issue is there,
    Http* Errors in XI
    Thanks

    http://server name:port/rwb, click message monitoring-- select msg. from component Adaptor Engine <SID> from Archive click display then click on start, getting below error
    "Cannot read archived messages; reason: Reading Messages from Archive failed. Reason: java.lang.Exception: XML DAS SELECT command failed with ErrorCode: 403; ErrorText: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html><head> <title>Error Report</title><style>td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}A:link A:visited A:active </style></head><body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"><table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"><tr bgcolor="#FFFFFF">    <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Helvetica" size="4" color="#666666"><b>  403 &nbsp Forbidden</b></font></td></tr><tr bgcolor="#3F73A3">    <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td>    <td height="23"><img width=1 height=1 border=0 alt=""></td>    <td align="right" height="23"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SAP NetWeaver Application Server 7.10 / AS Java 7.10 </b></font></td></tr><tr bgcolor="#9DCDFD">    <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td></tr></table><br><br><br><br><br><br><p><font face="Arial, Verdana, Helvetica" size="3" color="#000000"><b>  You are not authorized to view the requested resource.</b></font></p><p><font face="Arial, Verdana, Helvetica" size="2" color="#000000"><table><tr><td valign="top"><b> Details:</b></td><td valign="top"><PRE>No details available</PRE></font></td></tr></table></font></p></body></html>"
    But it's working fine when I select Database instead of Archive,
    thanks

  • HTTP Error 403.16 - Forbidden, Your client certificate is either not trusted or is invalid.

    Dear Experts,
    I have tried mutual authentication with sample website as per below link:
    http://itq.nl/testing-with-client-certificate-authentication-in-a-development-environment-on-iis-8-5/#comment-19427
    1. Created a Root certificate, client and server certificate based on this root certificate by using Makecert command as per below link:
    2. Import these certificates in Trusted Root Certification authority of both the stores (Local and Current user)
    3. Created a sample website with HTML page
    4.Hosted this website in IIS with HTTPS binding and selected the above server certifcate
    5. Enabled "Require SSL" and selected "Require" under SSL settings of website
    6. Exported the client certificate in base64 format --> Edited in notepad --> made the key into single line
    7. Placed the above key under Configuration editor --> system.webServer/security/authentication/iisClientCertificateMappingAuthentication --> one to one mapping with user credentials.
    8. I tried to access the website
    But, I ended with below error :(
    HTTP Error 403.16 - Forbidden
    Your client certificate is either not trusted or is invalid.
    Detailed Error Information:
    Module    IIS Web Core
    Notification    BeginRequest
    Handler    ExtensionlessUrlHandler-Integrated-4.0
    Error Code    0x800b0109
    Requested URL    https://localhost:443/
    Physical Path    E:\SampleRoot
    Logon Method    Not yet determined
    Logon User    Not yet determined
    Could you please let me know what I missed here.
    Note:
    I am using windows8, IIS8.0.
    Thanks in advance.
    Regards,
    M. Prasad Reddy.

    Hi Prasad,
      As per this case, I have been shared the corresponding details below
      1.First of all,make sure that you import the certificate whether it belongs to Trusted RootCertification or not .
        If that is the case ,Goto Microsoft Management Console (MMC), open the Certificates snap-in. 
        For instance, the certificate store that WCF is configured to retrieve X.509 certificates from, select the Trusted RootCertification Authoritiesfolder. Under the Trusted Root Certification Authorities folder, right-click the Certificatesfolder,
    point to All Tasks, and then click Import.
      2.you configured the server certificate as well, But check the client certificate whether have root certificate or not by following command?
    makecert -pe -n "CN=SSLClientAuthClient"
             -eku 1.3.6.1.5.5.7.3.2 -is root -ir localmachine -in WebSSLTestRoot
             -ss my -sr currentuser -len 2048
      3. Also check the Service Certificate whether its configured on the WCF Service side
      4.Make sure that you followed all the steps are done correctly from your given referred link below
    http://itq.nl/testing-with-client-certificate-authentication-in-a-development-environment-on-iis-8-5/#comment-19427
      5.Besides, please try to set the require SSL as ignore to see if you can access the website.
    If the above details cannot able to resolve this issue, please post your config file here.

  • HTTP Error 403 You are not authorized to view the requested resource

    Hi Experts,
    When I open the node "Hierarchie groups" I get the following error:  "Connection couldn't be recreated: 1 cause: Encountered invalid managed connection, last cause Couldn't execute interaction.  2 cause: Couldn't execute interaction. "
    In the log file I find the following:
    User MI_SERVADM, IP address
    HTTP request processing failed. HTTP error [403] will be returned. The error is [You are not authorized to view the requested resource.No details available].
    I used the User Service for administrator, I have not used the individual user for administrator.
    Regards, Gokhan

    Ah anyway I receive the above error even when I do a search in the node "Mobile Components".
    Now there's this in the LOG DefaultTrace (2 errors following)::
    1) Connection is already closed and no longer associated with a managed connection
    2) Exception occurred when processing Search:
    [EXCEPTION]
    com.sap.ip.mi.admin.core.ApplicationException: Connection couldn't be recreated: 1 cause: Encountered invalid managed connection, last cause Couldn't execute interaction.  2 cause: Couldn't execute interaction.
         at com.sap.ip.mi.ejb.admin.grouping.GroupingControllerBean.getHierarchy(GroupingControllerBean.java:730)
         at com.sap.ip.mi.ejb.admin.grouping.GroupingControllerBean.getHierarchy(GroupingControllerBean.java:580)
         at com.sap.ip.mi.ejb.admin.grouping.GroupingControllerLocalLocalObjectImpl0.getHierarchy(GroupingControllerLocalLocalObjectImpl0.java:547)
         at com.sap.ip.mi.admin.services.GroupingDelegate.getHierarchy(GroupingDelegate.java:81)
         at com.sap.ip.mi.admin.ui.HierarchyGroup.buildUpList(HierarchyGroup.java:252)
         at com.sap.ip.mi.admin.ui.wdp.InternalHierarchyGroup.buildUpList(InternalHierarchyGroup.java:409)
         at com.sap.ip.mi.admin.ui.Search.triggerSearch(Search.java:222)
         at com.sap.ip.mi.admin.ui.wdp.InternalSearch.triggerSearch(InternalSearch.java:286)
         at com.sap.ip.mi.admin.ui.Search.wdDoInit(Search.java:138)
         at com.sap.ip.mi.admin.ui.wdp.InternalSearch.wdDoInit(InternalSearch.java:272)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.onComponentCreated(ViewManager.java:258)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.fireComponentCreated(ComponentUsage.java:575)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:175)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141)
         at com.sap.lm.webadmin.mainframe.RenderingUtils.loadCurrentPlugin(RenderingUtils.java:189)
         at com.sap.lm.webadmin.mainframe.MainFrameView.wdDoModifyView(MainFrameView.java:272)
         at com.sap.lm.webadmin.mainframe.wdp.InternalMainFrameView.wdDoModifyView(InternalMainFrameView.java:1419)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
         at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:480)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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)
    Edited by: dpns22 on Feb 1, 2010 10:31 PM
    Edited by: dpns22 on Feb 1, 2010 10:59 PM

  • WL 5.1 and IIS - HTTP Error 403 - Access Forbidden problems

    I'm trying to hook IIS up to the evaluation version of WebLogic Server 5.1
    that I installed...
    I followed the instructions that I found on the Installing the Microsoft-IIS
    (proxy) plug-in page. I then copied HelloWorld.jsp into the
    d:\weblogic\myserver\public_html directory, and tried to bring it up in a
    browser by typing in localhost/HelloWorld.jsp. At this point, I got the
    following error:
    ** Begin error message **
    HTTP Error 403
    403.1 Forbidden: Execute Access Forbidden
    This error can be caused if you try to execute a CGI, ISAPI, or other
    executable program from a directory that does not allow programs to be
    executed.
    Please contact the Web server's administrator if the problem persists.
    ** End error message **
    I then tried adding a virtual directory called public_html to my default Web
    site. This didn't help. I even tried creating a directory called public_html
    inside public_html, setting execute privilages on it, and putting a copy of
    HelloWorld.jsp in there. This allowed me to type
    localhost/public_html/HelloWorld.jsp into my browser, and to see the JSP
    source code!?#...
    This is what my iisproxy.ini file looks like (It lives in d:\weblogic):
    ** Begin iisproxy.ini **
    # This file contains initialization name/value pairs
    # for the IIS/WebLogic plug-in.
    WebLogicHost=localhost
    WebLogicPort=7001
    WebLogicCluster=
    ConnectTimeoutSecs=20
    ConnectRetrySecs=2
    ** End iisproxy.ini **
    Any suggestions/help from someone who's done this before would be greatly
    appreciated. We can't run/evaluate the product before we can crawl and walk.
    Cheers...
    Dave Bruzzone
    WebCredenza, Inc.

    Thr problem is that you must set Execute rights to the IIS web at the
    Configuration settings (exactly as seen in the documentation).
    "Davide Bruzzone" <[email protected]> ha scritto nel messaggio
    news:8iubob$mgp$[email protected]..
    I'm trying to hook IIS up to the evaluation version of WebLogic Server 5.1
    that I installed...
    I followed the instructions that I found on the Installing theMicrosoft-IIS
    (proxy) plug-in page. I then copied HelloWorld.jsp into the
    d:\weblogic\myserver\public_html directory, and tried to bring it up in a
    browser by typing in localhost/HelloWorld.jsp. At this point, I got the
    following error:
    ** Begin error message **
    HTTP Error 403
    403.1 Forbidden: Execute Access Forbidden
    This error can be caused if you try to execute a CGI, ISAPI, or other
    executable program from a directory that does not allow programs to be
    executed.
    Please contact the Web server's administrator if the problem persists.
    ** End error message **
    I then tried adding a virtual directory called public_html to my defaultWeb
    site. This didn't help. I even tried creating a directory calledpublic_html
    inside public_html, setting execute privilages on it, and putting a copyof
    HelloWorld.jsp in there. This allowed me to type
    localhost/public_html/HelloWorld.jsp into my browser, and to see the JSP
    source code!?#...
    This is what my iisproxy.ini file looks like (It lives in d:\weblogic):
    ** Begin iisproxy.ini **
    # This file contains initialization name/value pairs
    # for the IIS/WebLogic plug-in.
    WebLogicHost=localhost
    WebLogicPort=7001
    WebLogicCluster=
    ConnectTimeoutSecs=20
    ConnectRetrySecs=2
    ** End iisproxy.ini **
    Any suggestions/help from someone who's done this before would be greatly
    appreciated. We can't run/evaluate the product before we can crawl andwalk.
    >
    Cheers...
    Dave Bruzzone
    WebCredenza, Inc.
    [isapi2.gif]

  • OAAD Picture upload - HTTP Error: 403 Forbidden

    Dear forum,
    When trying to upload a picture for our Q/A HR system in tx OAAD I get the error HTTP Error: 403 Forbidden. However, I can do it with no issues in our prod environment. Anyone has an idea why this is? I have checked SICF and icman is enabled. Does anyone have an suggestion? Hence it isnt portal communication I cant use httpwatch, which most likely could have told me whats wrong.
    I hope someone is able to comment on this issue.
    Thanks in advance!
    Kind Regards,
    Soren

    Dear Friis,
    We have a steps of configurations that needs to be completed for the photo upload to be working. As you say the same is working in the production system, I hope you have the steps with you.
    Most common things that needs to be checked in this scenario are,
    1. HTTP service availability through the configured profile parameter in the system
    2. Restart after the profile parameter change
    3. Content Server node activation in SICF transaction
    4. User ID and Password to be mentioned in the SICF service as communications or system user
    5. Other checks for the content repository and the number range
    You can also try repeatedly, to upload the pic (in a JPG format) - because most usually the first trial ends in a failure for the HTTP service with a 403 Forbidden error message.
    Let me know your response and the steps you had followed for the config.
    Thank you
    Regards,
    Vineeth

  • UPK - Player gives HTTP Error 403 error

    I have created a animation using UPK. A player.exe was generated. It was playing fine on my local drive but when I post it to shared interface it gives me this error -
    Contact localhost:3282 home
    HTTP Error 403 - Forbidden
    Internet Explorer
    Have anyone of you encountered this? Please help.
    Thanks

    Jay,
    You should use this URL:
    https://ipaddress/certsrv/mscep
    If you try to get the cert from an http address, you will get an error.  You should be using https.  Also, the mscep.dll should not be part of the URL.
    You can test this connectivity from any browser by putting that URL in the sddress bar.  You should see a page similar to this:
    Please Rate Helpful posts and mark this question as answered if, in fact, this does answer your question.  Otherwise, feel free to post follow-up questions.
    Charles Moreton

  • Example Basicresponse: HTTP Error 403 - Forbidden

    Hi,
    i installed the developer edition of ocms.
    The eclipse plugin works fine.
    I was able to deploy the "thirdpartycallcontrol" and to access it via http://localhost:8888/tpcc.
    BUT
    the basicresponse example does not work. I can deploy it but on
    http://localhost:8888/basicresponse
    i get HTTP Error 403 - Forbidden
    Is this not accessible via webfrontend?
    How can i see if this is working? In the documentation the use case is missing....

    Hi HEWizard,
    Basicresponse is a SIP only application, hence it's not available via a web front end. It can be accessed via a test SIP testing tool such as sipp: http://sipp.sourceforge.net/
    Hope this helps,
    Adam

  • Safari HTTP error 403

    I am connected to the internet - email works fine, evernote syncronises etc.  But on ANY web page I am getting a HTTP Error 403: The service you requested is restricted and is not available to your browser.
    The restriction can be based on your IP address, hostname, browser software, time of day of other variables well.
    IP address - Works for other services
    hostname - not sure how this impacts anything
    browser software - brand new Pad2 - should be ok - Apple?
    time of day - erm just how is this important
    other variables - ah - probably that then -
    Anyone seen this before?
    Greg

    Error 403 means that you don't have the permission to view that particular page.
    You can try these steps.
    Go step by step and test.
      Quit Safari.
      Hold the shift key down and relaunch Safari.
    Delete cookies
    Safari > Preferences >  Privacy > Cookies and other website data:
    Press the “Remove All Website Data” button.
    It will take a while to finish.
    Empty Caches
    Safari > Preference > Advanced
    Checkmark the box for "Show Develop menu in menu bar".
    Develop menu will appear in the Safari menu bar.
    Click Develop and select "Empty Caches" from the dropdown.

  • Resolve http error 403.4 in firefox

    Hi! I am trying to open icicidirect website but every tine after login home page comes but when I try to move to another page in website , it gives me this error ''' Type http:// at the beginning of the address you are attempting to reach and press ENTER.
    HTTP Error 403.4 - Forbidden: SSL is required to view this resource.
    Internet Information Services (IIS)'''[[Knowledge Base Article]].
    kindly solve the issue as its important.I have tries to type https also but no use.
    Thanks Deepika

    Use https://221.135.134.52/vodacts/
    That gives me a certificate error because the server doesn't send an intermediate certificate that chains to a build-in root certificate.

  • OHS VirtualHost only SSL - redirect to equivalent of IIS HTTP Error 403.4 - Forbidden: SSL is required to view this resource

    Hi,
    I'm completely new to OHS and have been asked to ensure that a URL that goes to OHS should only be accessible on HTTPS, if accessed by HTTP it should go to the equivalent of IISs
    HTTP Error 403.4 - Forbidden: SSL is required to view this resource.
    As OHS is the frontend to our SOA installation we have specific files under /moduleconf/ for the virtualhosts, an example of one is below. 
    Can anyone give me any clues/best practice to only allow this VirtualHost to be allowed on HTTPS/SSL and to not redirect non SSL to SSL but to an error page like the equivalent mentioned above.
    Any guidance would be greatly appreciated.  Many thanks
    <VirtualHost *:443>
      ServerName testhub.example.com:443
      RewriteEngine On
      RewriteOptions inherit
      RewriteRule ^$ /osb/hub.asmx [NC,P]
      RewriteRule ^/$ /osb/hub.asmx [NC,P]
      RewriteRule ^/hub\.asmx$ /osb/hub.asmx [NC,P]
    <Location /sbinspection.wsil >
      SetHandler weblogic-handler
      WebLogicCluster OSB1:8011,OSB2:8011
    </Location>
    <Location /sbresource >
      SetHandler weblogic-handler
      WebLogicCluster OSB1:8011,OSB2:8011
    </Location>
    <Location /osb >
      SetHandler weblogic-handler
      WebLogicCluster OSB1:8011,OSB2:8011
    </Location>
    <Location /alsb >
      SetHandler weblogic-handler
      WebLogicCluster OSB1:8011,OSB2:8011
    </Location>
    <IfModule ossl_module>
      SSLEngine on
      SSLProtocol nzos_Version_1_0 nzos_Version_3_0_With_2_0_Hello nzos_Version_3_0
      SSLCipherSuite SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA,SSL_RSA_WITH_3DES_EDE_CBC_SHA,SSL_RSA_WITH_DES_CBC_SHA,TLS_RSA_WITH_AE
    S_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA
      SSLVerifyClient none
      SSLWallet  "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/keystores/host"
      SSLProxyEngine On
      SSLProxyWallet  "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/keystores/host"
      SSLCRLCheck Off
    </IfModule>
    </VirtualHost>

    Use https://221.135.134.52/vodacts/
    That gives me a certificate error because the server doesn't send an intermediate certificate that chains to a build-in root certificate.

  • HTTP Error 403 - Forbidden Error Accessing Simplest Example

    If I follow the instructions for creating the SIMPLEST example in the "iFS Online Resources" document, everything seems to work until the very last step. When I click on one of my sample objects a new window is launched for the JSP, but it gets an HTTP-403 error in it.
    Anone have any ideas? Thanks.

    Strangely enough, we're having no problems viewing the XML case files from within the JSW interface, they call the InsuranceForm jsp without any errors - which would indicate that the Java beans are in the right place. Yes?
    The problem we're getting is trying to log into the iFS repository via the URL http://<iFS Server>/public/examples/insuranceApp/src/login.jsp
    as per the demo instructions, we get HTTP Error 403 - Forbidden. I checked the permissions on the adk.jar file as per Monty Burns posts, and it's world readable. What gives?
    We've installed the 1.0.8.3 patch and the 8.1.6.0.1 JDK. NT Server 4, SP6, 8.1.6 database.
    Thanks in advance for your help,
    Cheers
    Geoff.

  • HTTP Error 403 - Forbidden on Cisco ISE and SCEP RA

    Dear Experts,
    We are in process of deploying ISE 1.2 in our environment for BYOD.
    The initial step of this process is to configure ISE as an SCEP Proxy and it requires certain configuration on the local CA. We have done all the required configurations on the local CA server.
    Now, when we try to connect ISE with the local CA using SCEP RA Profiles, it gives "HTTP Error 403 - Forbidden". The URL we are using is http://ipaddress/certsrv/mscep/mscep.dll.
    It seems that the local CA is not letting the ISE access the mscep.dll file. Now I dont understand how to allow ISE to access this file or the url. Please advise if there is any step by step process guide. Although, I have followed the ones from Cisco but it doesn't state how to give ISE the required rights for accessing mscep.dll.
    Thanks in advance.
    Jay

    Jay,
    You should use this URL:
    https://ipaddress/certsrv/mscep
    If you try to get the cert from an http address, you will get an error.  You should be using https.  Also, the mscep.dll should not be part of the URL.
    You can test this connectivity from any browser by putting that URL in the sddress bar.  You should see a page similar to this:
    Please Rate Helpful posts and mark this question as answered if, in fact, this does answer your question.  Otherwise, feel free to post follow-up questions.
    Charles Moreton

  • HTTP error [403] in "Add Forums Administrator User"-iView (Forum)

    Hi All,
    I need help with installing the forum functionality.
    When I open the "Add Forums Administrator User"-iView I always get the following error message:
    <i>403   Forbidden
    You are not authorized to view the requested resource.</i>
    In the log-file I found the following message:
    <i>User tfelp4, IP address
    HTTP request processing failed. HTTP error [403] will be returned. The error is [You are not authorized to view the requested resource.No details available].</i>
    I must say that my useraccount has Superadmin-Permissions...
    The "Forum"-iView works without problems, but there are no forum catagories, cause they must be installed for using.
    Hope someone can help me
    Thanks in advance
    Steve

    Hi Trevor,
    thanks for your reply. What does it mean <i>"The actuall permissions must be given on the WEBAS"</i>? In my understanding the Userprofiles and the assignment of permissions to a profiles are stored in the UME. In my mind  I can do that within the portal environment.
    Hope you can help me...
    @All: Does anybody has similar problems?
    Bye and Thanks
    Steve
    null

Maybe you are looking for