Error 403 Forbidden, while publishing a WS

Hi all,
i have defined a web-service in SAP Workbench. now i'm trying to publish it and it simply doesn't work, whatever i try.
after i defined a binding in the SOAMANAGER and want the WSDL for it to be shown, i get
Error 403: Forbidden. Anyone ideas?
im pretty fresh around web services in SAP, so i tried another scenario taken from help-sites.  in tr-cd WSPUBLISH i get proxy instantiation error. (i created the Service registry also by myself in tr-cd WSPARAM).
thnx 4 ur help in advance!!!
regards
vasyl

          Hi Bijan,
          thats to less info. We need a little bit more to help you.
          Try looking at the console and tell us what you see.
          Which Version of WLS are you running ??
          fear
          Bijan Mohanty <[email protected]> wrote:
          >Hi,
          >
          >I have deployed a webapp(the war file)by placing it in the config/mydomain/applications
          >dir. The web app is deployed successfully and can be seen in the weblogic
          >console. But while accessing the servlet I am getting the following
          >error. Could somebody please tell me what needs to be done to fix this.
          >
          >Thanks a lot.
          >
          >Bijan.
          >
          >Error 403--Forbidden
          >From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
          >10.4.4 403 Forbidden
          >The server understood the request, but is refusing to fulfill it. Authorization
          >will not help and the request SHOULD NOT be repeated. If the request
          >method was not HEAD and the server wishes to make public why the request
          >has not been fulfilled, it SHOULD describe the reason for the refusal
          >in the entity. This status code is commonly used when the server does
          >not wish to reveal exactly why the request has been refused, or when
          >no other response is applicable
          

Similar Messages

  • Getting "Error 403--Forbidden" while accessing ADF bookmarked URL

    Hi,
    Here am trying to work with an ADF application to suport bookmarking.
    Following are the steps I did to create a sample application.
    Created a bounded task-flow (user-details.xml), which has the "Method call" as default activity along with an another view activity(userData.jsff page).
    This task-flow takes an input parameter "Id" to display user details. In the method call activity user data will be initialized using the given input parameter and then the data will be displayed using userData.jsff page.
    Created a view activity (details.jspx page) in adfc-config.xml file.
    Marked the "details.jspx" file as bookmark-able by changing "Bookmark property to true" and given a Bookmark URL Parameter "Name is Id and Value is #{pageFlowScope.user_id}".
    Dropped the bounded task-flow user-details.xml as a region into the details.jspx file.
    Now the user_id which is coming as URL Parameter will be passed to user-details.xml task-flows input parameter value.
    Created users.jspx page which lists all the users as home page. In the users.jspx page we'll have a link to user details page with a parameter Id.
    By running the application will get users page. When I click on the user details link in the users page, the app showing user details page as expected.
    Now I bookmarked the user details page. If I open the bookmarked page in the same tab, it is working fine. But when I open this bookmark in a new tab getting the "Error 403--Forbidden" response.
    Bookmarked URL: localhost:7101/BookmarkTestApp-ViewController-context-root/faces/user_details?id=123&_afrWindowMode=0&_afrLoop=4884151149818&_adf.ctrl-state=35yghmx4f_18
    When I click the above bookmark in another tab the url is processing for few seconds ( 2 to 3 seconds) and converts to localhost:7101/BookmarkTestApp-ViewController-context-root/ and giving 403 response. At this time it is not touching my beans at all (verified this by running the server in debug mode).
    Web.xml looks like:
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
             xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
             version="2.5" xmlns="http://java.sun.com/xml/ns/javaee">
      <context-param>
        <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
        <param-value>client</param-value>
      </context-param>
      <context-param>
        <description>If this parameter is true, there will be an automatic check of the modification date of your JSPs, and saved state will be discarded when JSP's change. It will also automatically check if your skinning css files have changed without you having to restart the server. This makes development easier, but adds overhead. For this reason this parameter should be set to false when your application is deployed.</description>
        <param-name>org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION</param-name>
        <param-value>false</param-value>
      </context-param>
      <context-param>
        <description>Whether the 'Generated by...' comment at the bottom of ADF Faces HTML pages should contain version number information.</description>
        <param-name>oracle.adf.view.rich.versionString.HIDDEN</param-name>
        <param-value>true</param-value>
      </context-param>
      <filter>
        <filter-name>trinidad</filter-name>
        <filter-class>org.apache.myfaces.trinidad.webapp.TrinidadFilter</filter-class>
      </filter>
      <filter>
        <filter-name>adfBindings</filter-name>
        <filter-class>oracle.adf.model.servlet.ADFBindingFilter</filter-class>
      </filter>
      <filter-mapping>
        <filter-name>trinidad</filter-name>
        <servlet-name>Faces Servlet</servlet-name>
        <dispatcher>FORWARD</dispatcher>
        <dispatcher>REQUEST</dispatcher>
      </filter-mapping>
      <filter-mapping>
        <filter-name>adfBindings</filter-name>
        <servlet-name>Faces Servlet</servlet-name>
        <dispatcher>FORWARD</dispatcher>
        <dispatcher>REQUEST</dispatcher>
      </filter-mapping>
      <listener>
        <listener-class>oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack</listener-class>
      </listener>
      <servlet>
        <servlet-name>Faces Servlet</servlet-name>
        <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
        <load-on-startup>1</load-on-startup>
      </servlet>
      <servlet>
        <servlet-name>resources</servlet-name>
        <servlet-class>org.apache.myfaces.trinidad.webapp.ResourceServlet</servlet-class>
      </servlet>
      <servlet>
        <servlet-name>BIGRAPHSERVLET</servlet-name>
        <servlet-class>oracle.adfinternal.view.faces.bi.renderkit.graph.GraphServlet</servlet-class>
      </servlet>
      <servlet>
        <servlet-name>BIGAUGESERVLET</servlet-name>
        <servlet-class>oracle.adfinternal.view.faces.bi.renderkit.gauge.GaugeServlet</servlet-class>
      </servlet>
      <servlet>
        <servlet-name>MapProxyServlet</servlet-name>
        <servlet-class>oracle.adfinternal.view.faces.bi.renderkit.geoMap.servlet.MapProxyServlet</servlet-class>
      </servlet>
      <servlet>
        <servlet-name>GatewayServlet</servlet-name>
        <servlet-class>oracle.adfinternal.view.faces.bi.renderkit.graph.FlashBridgeServlet</servlet-class>
      </servlet>
      <servlet-mapping>
        <servlet-name>Faces Servlet</servlet-name>
        <url-pattern>/faces/*</url-pattern>
      </servlet-mapping>
      <servlet-mapping>
        <servlet-name>resources</servlet-name>
        <url-pattern>/adf/*</url-pattern>
      </servlet-mapping>
      <servlet-mapping>
        <servlet-name>resources</servlet-name>
        <url-pattern>/afr/*</url-pattern>
      </servlet-mapping>
      <servlet-mapping>
        <servlet-name>BIGRAPHSERVLET</servlet-name>
        <url-pattern>/servlet/GraphServlet/*</url-pattern>
      </servlet-mapping>
      <servlet-mapping>
        <servlet-name>BIGAUGESERVLET</servlet-name>
        <url-pattern>/servlet/GaugeServlet/*</url-pattern>
      </servlet-mapping>
      <servlet-mapping>
        <servlet-name>MapProxyServlet</servlet-name>
        <url-pattern>/mapproxy/*</url-pattern>
      </servlet-mapping>
      <servlet-mapping>
        <servlet-name>resources</servlet-name>
        <url-pattern>/bi/*</url-pattern>
      </servlet-mapping>
      <servlet-mapping>
        <servlet-name>GatewayServlet</servlet-name>
        <url-pattern>/flashbridge/*</url-pattern>
      </servlet-mapping>
      <mime-mapping>
        <extension>swf</extension>
        <mime-type>application/x-shockwave-flash</mime-type>
      </mime-mapping>
      <jsp-config>
        <jsp-property-group>
          <url-pattern>*.jsff</url-pattern>
          <is-xml>true</is-xml>
        </jsp-property-group>
      </jsp-config>
    </web-app>
    Am I missing any thing here.
    Thanks in advance.
    -Gopal.

    https://blogs.oracle.com/DavidGiammona/entry/why_do_i_get_this_error_403_--

  • Error 403--Forbidden while trying to access servlet

              Hi All,
              I am very new to Weblogic server. I have downloaded the 6.1 version of Weblogic
              application server. I tried a simple example in which I have an HTML which calls
              a servlet. I have deployed it on weblogic server using auto deployment feature.
              But when I try to access the html form, it gives me the following error.
              Please can anybody suggest a solution to this problem?
              Thanks,
              Vani
              Error 403--Forbidden
              From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
              10.4.4 403 Forbidden
              The server understood the request, but is refusing to fulfill it. Authorization
              will not help and the request SHOULD NOT be repeated. If the request method was
              not HEAD and the server wishes to make public why the request has not been fulfilled,
              it SHOULD describe the reason for the refusal in the entity. This status code
              is commonly used when the server does not wish to reveal exactly why the request
              has been refused, or when no other response is applicable.
              

    The demo license limits access from browsers to three unique IP addresses.
              When accessed by a fourth IP address, WLS returns '403'. You should see a
              message in the log file about the demo license.
              Mike
              "Vani" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Hi All,
              > I am very new to Weblogic server. I have downloaded the 6.1 version of
              Weblogic
              > application server. I tried a simple example in which I have an HTML which
              calls
              > a servlet. I have deployed it on weblogic server using auto deployment
              feature.
              > But when I try to access the html form, it gives me the following error.
              >
              > Please can anybody suggest a solution to this problem?
              > Thanks,
              > Vani
              >
              > -----------------------------------------------------------------
              >
              > Error 403--Forbidden
              > From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
              > 10.4.4 403 Forbidden
              > The server understood the request, but is refusing to fulfill it.
              Authorization
              > will not help and the request SHOULD NOT be repeated. If the request
              method was
              > not HEAD and the server wishes to make public why the request has not been
              fulfilled,
              > it SHOULD describe the reason for the refusal in the entity. This status
              code
              > is commonly used when the server does not wish to reveal exactly why the
              request
              > has been refused, or when no other response is applicable.
              >
              > -----------------------------------------------------------------
              

  • Error 403-forbidden from IE5 while authenticating a user through NT Realm

    Hi,
    Before posting this request, I checked the forum until Sep.18 to see if nobody
    else experienced my problem, but in vain.
    I am using WLS6.1Sp1 under NT4
    I would like that NT users for defined NT Primary Domain Controller authenticate
    themselves before accessing a web app. For that, I followed thoroughly the BEA
    Doc to get the config.xml, web.xml, weblogic.xml and filerealm.properties correctly
    configured.
    The <auth-method> is set to FORM. The <security-role> and <security-role-assignment>
    are also set with business roles and principals from the NT PDC. the <security-constraint>
    with all the sub-tags are also defined. etc.etc. When I use the WL console, to
    check users and groups lists, it works fine although it takes a lot of time before
    being displayed (15 to 20 minutes !!!).
    Through a Login.jsp, the user enters his/her login name and password. The result
    is that I get the following message :
    "Error 403--Forbidden
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it. Authorization
    will not help and the request SHOULD NOT be repeated. If the request method was
    not HEAD and the server wishes to make public why the request has not been fulfilled,
    it SHOULD describe the reason for the refusal in the entity. This status code
    is commonly used when the server does not wish to reveal exactly why the request
    has been refused, or when no other response is applicable."
    No trace in the log files. No warning . Nothing.
    My questions are:
    1- Has somebody already experienced this?
    2- Could you then help me ?
    By advance , thank you very much.
    Athmani H.
    Note : I can provide you through email the config.xml, web.xml, weblogic.xml and
    filerealm.properties and the concerned .jsp files on demand

    Hi Jerry,
    Many thanks for your interest and your help.
    weblogic.properties file for WLS 6.1 SP1? There is none... I do have a filerealm.properties. I didn't state that I was using a weblogic.properties
    file.
    I checked the URL you proposed. I changed the <Auth-method> from FORM into BASIC.
    A pop-up window is displayed requesting the user to enter username and password.
    The result is that I get a web page displaying an Error 404 --not found.
    Here is the complete error message :"Error 404--Not Found
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.5 404 Not Found
    The server has not found anything matching the Request-URI. No indication is given
    of whether the condition is temporary or permanent.If the server does not wish
    to make this information available to the client, the status code 403 (Forbidden)
    can be used instead. The 410 (Gone) status code SHOULD be used if the server knows,
    through some internally configurable mechanism, that an old resource is permanently
    unavailable and has no forwarding address."
    The message is displayed when the browser tries to resolve the following URL :http://localhost:7001/examplesWebApp/j_security_check
    Having said that, I had already configured the <security-role-assignement> with
    role-name and principals in weblogic.xml, as well as the <security-role> tag in
    web.xml.
    Thanks for your help
    Cheers
    Habib
    Jerry <[email protected]> wrote:
    Hi Athmani,
    weblogic.properties file for WLS 6.1 SP1? There is none... weblogic.properties
    is in WebLogic
    5.1 and lower -- it was changed to config.xml for WLS 6.0 .. what are
    you using your
    weblogic.properties file for?
    Anyways,
    I have gotten NTRealms to successfully work with WLS 6.1, with security
    on a web app, allowing
    NT users to access certain resources. This stuff works.
    Since you can see your users and groups through the console (even though
    it takes a while) I
    think that your NTRealm setup is okay.
    I would guess that you have a problem with your deployment descriptors
    in your web
    application.
    There are quite a few posts in this newsgroup that illustrate how to
    set up security
    constraints on resources in your web app with the deployment descriptors.
    For example, check out
    http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.security&item=6244&utag=
    Let me know how it goes, okay?
    Cheers,
    Joe Jerry
    "Athmani H." wrote:
    Hi,
    Before posting this request, I checked the forum until Sep.18 to seeif nobody
    else experienced my problem, but in vain.
    I am using WLS6.1Sp1 under NT4
    I would like that NT users for defined NT Primary Domain Controllerauthenticate
    themselves before accessing a web app. For that, I followed thoroughlythe BEA
    Doc to get the config.xml, web.xml, weblogic.xml and filerealm.propertiescorrectly
    configured.
    The <auth-method> is set to FORM. The <security-role> and <security-role-assignment>
    are also set with business roles and principals from the NT PDC. the<security-constraint>
    with all the sub-tags are also defined. etc.etc. When I use the WLconsole, to
    check users and groups lists, it works fine although it takes a lotof time before
    being displayed (15 to 20 minutes !!!).
    Through a Login.jsp, the user enters his/her login name and password.The result
    is that I get the following message :
    "Error 403--Forbidden
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it. Authorization
    will not help and the request SHOULD NOT be repeated. If the requestmethod was
    not HEAD and the server wishes to make public why the request has notbeen fulfilled,
    it SHOULD describe the reason for the refusal in the entity. This statuscode
    is commonly used when the server does not wish to reveal exactly whythe request
    has been refused, or when no other response is applicable."
    No trace in the log files. No warning . Nothing.
    My questions are:
    1- Has somebody already experienced this?
    2- Could you then help me ?
    By advance , thank you very much.
    Athmani H.
    Note : I can provide you through email the config.xml, web.xml, weblogic.xmland
    filerealm.properties and the concerned .jsp files on demand

  • Ajax submit failed: error =403, Forbidden IS SHOWN WHILE REGISTERING

    can't register get 'Ajax submit failed: error =403, Forbidden'
    what do I need to do?

    Hi there, clear your browsers cached history and restart the browser. If that doesn't work try using another browser type.
    All the best.
    If my reply helped you, feel free to click on the Kudos button (hover over the "thumbs up").
    If my reply solved your problem please click on the Accepted Solution button so other Forum users may benefit from viewing the post.
    I am an HP employee.

  • HTTP Error 403 - Forbidden  error when auto including a jspx page

    Hi All -
    We have a situation where one of different reports pages gets included inside a main reports page based on user selection via a selectOneChoice control.
    But when the Reports Main page tab is clicked for the first time we get a "You are not authorized to view this page" HTTP Error 403 - Forbidden error.
    Upon clicking "Refresh" and then clicking the Reports Main page tab again, the page renders correctly.
    This is our code snippet. All the report related pages(MainPage.jspx, Schedule.jspx and Budget.jspx) are inside a reports folder under the context root. Please help.
    Thanks for your time.
    MainPage.jspx
    =====================
    Here I have a selection box, and based on the user selection I include different JSPX pages. The page Definition of this page
    contains all the executables and the bindings of the included pages also.
    <af:selectOneChoice value="#{backing_Reports.measureSelected}"
    label="Measure" unselectedLabel="Select One"
    id="selectmeasure" autoSubmit="true"
    immediate="true">
    <af:selectItem label="Schedule Data"
    value="Schedule.jspx"/>
    <af:selectItem label="Budget Data"
    value="Budget.jspx"/>
    </af:selectOneChoice>
    <af:panelGroup>
    <jsp:include page="${backing_Reports.measureSelected}" flush="true"/>
    </af:panelGroup>
    Faces Config:
    ===================
    <navigation-rule>
    <from-view-id>*</from-view-id>
    <navigation-case>
    <from-outcome>GlobalHome</from-outcome>
    <to-view-id>/pages/Welcome.jspx</to-view-id>
    <redirect/>
    </navigation-case>
    <navigation-case>
    <from-outcome>GlobalReports</from-outcome>
    <to-view-id>/reports/MainPage.jspx</to-view-id>
    </navigation-case>
    <!-- 1. Reports menu tab item -->
    <managed-bean>
    <managed-bean-name>menuItem_Reports</managed-bean-name>
    <managed-bean-class>cs.view.menu.MenuItem</managed-bean-class>
    <managed-bean-scope>session</managed-bean-scope>
    <managed-property>
    <property-name>label</property-name>
    <value>#{resources['scorecard.menu.reports']}</value>
    </managed-property>
    <managed-property>
    <property-name>viewId</property-name>
    <value>/reports/MainPage.jspx</value>
    </managed-property>
    <managed-property>
    <property-name>outcome</property-name>
    <value>GlobalReports</value>
    </managed-property>
    </managed-bean>
    :

    We have solved this, temproarily. But don't know if this is the best method to do this. Please post if somepne has a better way of doing this.
    While debugging we found that the ${backing_Reports.measureSelected} field which was set to a default value in backing bean was returned as null when the page renders for the first time. So we had a work around like this in our MainPage.jspx
    <af:panelBox width="80%" partialTriggers="selectmeasure"
    inlineStyle="margin:40.0px;">
    <af:panelGroup>
    <jsp:include page="${backing_Reports.measureSelected==null?'BlankPage.jspx':backing_Reports.measureSelected}"
    flush="true"/>
    </af:panelGroup>
    </af:panelBox>
    Thanks.

  • Error 403--Forbidden - From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.

    Hi, I have a problem with WebLogic Server: 10.3.5.0.
    I need to set that anyone who sees my enterprise application can view the website but not how. I always displays an error.
    The error is:
    Error 403--Forbidden
    From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
    10.4.4 403 Forbidden
    The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
    Can you help me?

    When I'm working with web servers, and I've not worked with weblogic for quite a while, it has always been rights that have been the gotcha for the 403 error. You need to make sure that if you want everyone to be able to brouse the given folder, you need public read and execute rights on the contents.

  • [SOLVED] The requested URL returned error: 403 Forbidden

    Hi guys
    (sory for my english
    I have a problem with packer -Syu
    the output:
    Proceed with installation? [Y/n] y
    Edit openbox-menu PKGBUILD with $EDITOR? [Y/n] n
    ==> Making package: openbox-menu 0.3.6.8-1 (Tue Feb 12 15:52:19 UTC 2013)
    ==> Checking runtime dependencies...
    ==> Checking buildtime dependencies...
    ==> Retrieving Sources...
      -> Downloading openbox-menu-0.3.6.8.tar.bz2...
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
      0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
    curl: (22) The requested URL returned error: 403 Forbidden
    ==> ERROR: Failure while downloading openbox-menu-0.3.6.8.tar.bz2
        Aborting...
    The build failed.
    for full detials:
    http://pastebin.com/Acq0uY78
    iam try another mirrors... but i get same problen
    i install tor (for use tsocks or torify) but its dont work in my country
    HELP ME PLZ
    thanks
    Last edited by tareef (2013-02-14 19:39:07)

    It's http://mimarchlinux.googlecode.com/file … .8.tar.bz2, just as the PKGBUILD says.
    Edit:
    If something is broken, you should ask on the AUR page for the maintainer to fix the PKGBUILD https://aur.archlinux.org/packages/openbox-menu/, but the PKGBUILD worked for me.
    tareef wrote:
    for full detials:
    http://pastebin.com/Acq0uY78
    iam try another mirrors... but i get same problen
    i install tor (for use tsocks or torify) but its dont work in my country
    openbox-menu is from the AUR and not from the repos, so changing mirrors won't do anything here. You might want to read on what AUR is and deal with the issues with the signatures first.
    Last edited by karol (2013-02-13 00:10:04)

  • Error message when trying to sign in to HP ePrint "ajax submit failed: error = 403, forbidden"

    HP Photosmart 7525
    Windows 7
    Ajax submit failed: error = 403, Forbidden
    Installed new printer: Photosmart 7525
    I am trying to set up my ePrint account and add my printer and it won't let me sign in or create a new account.
    Thanks for your help!
    Deb
    This question was solved.
    View Solution.

    One can also restart the computer.After it shuts down leave it off for at least a minute and then reattempt access the site once computer is back on and running. I would also check to make sure that Java is up to date and that Adobe Flash is up to date. 
    I am a former employee of HP...
    How do I give Kudos?| How do I mark a post as Solved?

  • Server Error  403 - Forbidden: Access is denied. You do not have permission to view this directory or page using the credentials that you supplied.

    Hi,
    I`d like to get your advice on Server Error 403 - Forbidden: Access is denied. I use to visit a webpage with no issues so far but now i getting this error each time i`m trying to get into. Any ideas in how to solve it? A step to step process will be highly appreciated.
    Thanks.
    PS, I`m using the latest safari 8.0.3 and OS X 10.10.2.

    It's an error message from the web server, not from Safari. There's a slight chance that you might be able to clear it as follows.
    From the Safari menu bar, select
              Safari ▹ Preferences... ▹ Privacy ▹ Remove All Website Data...
    and confirm. Test.

  • I tried to access my website, but Firefox threw the error: 403 Forbidden, you don't have the permissions to view.

    My website - Mousenstein.com - is under construction w/Dreamweaver + Flash.
    I uploaded my files to my server.
    I opened Firefox and entered the URL:
    http://www.mousenstein.com
    The error "403 Forbidden" appeared, and ...
    You do not have the permissions to access.
    I have tried to upload my site countless times, but never successfully - it is a huge headache. That said, I have never gotten the "403 Forbidden - no permissions" before.
    All other failures threw the error "404, can not locate the URL "/" on this server.
    Any help will be enormously appreciated.
    P.S. : Are there permissions preferences on Firefox? I found one under Tools Menu, but it didn't seem to address my problem.
    Thanks

    I get the same thing with Firefox, IE8, Opera, and Safari. It isn't a Firefox only problem.
    Are you new to that webhosting service? <br /> Have you ever uploaded web pages to that same web hosting service previously, pages that worked after an upload? <br /> Are those pages listed as ''' "public" ''' pages in your web hosts control panel?
    My suggestion is to "download" your homepage and associated files & images from your PC, up to the server, using your web hosts control panel and see how that works.
    Beyond that, I suspect that you might have missed an important setting in Dreanweaver for uploading to the web host's server. You might try asking about this issue at a Dreamweaver support forum.

  • Can't sign up for eprintcenter-I get this error ---Ajax submit failed: error = 403, Forbidden

    Bought my 6700 printer yesterday.  Set it all up, prints fine.  Got the print out that tells me to go to the eprintcenter.com and "sign up and enter your printer code." 
    Every time I enter any information, I get this error code:  Ajax submit failed: error = 403, Forbidden
    I've tried entering my personal email, the eprint email--in short I've tried everything and can't register for an account so I can customize my printer email address, etc.  Can some one help?

    Tifmel,
    I do apologize that you are having this issue. If you are still having this issue, I would suggest using a different web browser (i.e. internet explorer, google chrome, mozilla firefox). There are more that are available but those are just a few examples. I sure hope you can get everything worked out. Thanks again!!!!
    Feel free to repost if you have any further questions, comments, or concerns.
    If I have SOLVED your issue, please feel free to provide KUDOS and make sure you mark this thread as SOLUTION PROVIDED!
    Although I work for HP, my posts and replies are my own opinion and not those of HP.

  • What does "ajax submit failed: error = 403, forbidden" mean when trying to sign up for eprint?

    what does "ajax submit failed: error = 403, forbidden" mean when trying to sign up for eprint?

    Hi,
    Please use different browser such as Firefox or Chrome and try again.
    Regards.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

  • Eprint error creating account: Ajax submit failed: error = 403, Forbidden

    I am trying to create an eprint account. but when I hit submit I get:
    Ajax submit failed: error = 403, Forbidden
    I am running from a mac with OSX 10.8. And a new HP Photosmart 6515. The browser is Safari version 6.0.
    I've tried different namse, screen names passwords etc....
    THANKS,
    Tim
    This question was solved.
    View Solution.

    Hi there, this issue can usually be resolved by deleting your browsers cache and restarting the browser. Other forum users have confirmed that using an alternative browser type can also work (Mozilla FF and Google Chrome have both been cited).
    Try these suggestions and see how you get on.
    If my reply helped you, feel free to click on the Kudos button (hover over the "thumbs up").
    If my reply solved your problem please click on the Accepted Solution button so other Forum users may benefit from viewing the post.
    I am an HP employee.

  • Eprint login error: Ajax submit failed: error = 403, Forbidden.

    Why do I keep getting this error when trying to log in  to eprint website to manage my printer: Ajax submit failed: error = 403, Forbidden.

    Hi,
    Please perfer the following the check.
    1. Try to view the site in a different web browser to see if that's the issue. Normally, Internet Explorer, Google Chrome, Firefox, and Safari all display the website properly. Try one or two of those (other than the one you've been using) and it should do the trick.
    2. If that doesn't work, try resetting Internet Explorer's default settings by clicking "Tools" (on the top menu bar), "Internet Options" (usually at the bottom of that list), "Advanced" (far-right tab), and "Reset" (towards the bottom-right of that box). After resetting the defaults, try viewing the ePrint Settings area again.
    Although I am an HP employee, I am speaking for myself and not for HP.
    --Say "Thanks" by clicking the Kudos Star in the post that helped you.
    --Please mark the post that solves your problem as "Accepted Solution"

Maybe you are looking for