HTTP 405 Error | Adobe Higher Education
Skip to main content
V
vineetp40789287
Level 2
September 24, 2018

HTTP 405 Error

  • September 24, 2018
  • 6 risposte
  • 11627 visualizzazioni

I'm facing issue in uploading the java bundles in felix console.

whenever I'm trying to upload a bundle , my browser is not responding for some time and after that  its throws http 405 error.

I tried uploading lower size bundles ,still getting same error.

I'm using 6.1.

    Questo argomento è stato chiuso alle risposte.

    6 risposte

    smacdonald2008
    smacdonald2008
    Level 10
    September 24, 2018

    Its hard for commnity to suggest a fix without more information. Please post any log messages that you are seeing

    V
    vineetp40789287Autore
    Level 2
    September 25, 2018

    org.apache.sling.security.impl.ReferrerFilter Rejected empty referrer header for POST request to /system/console/bundles

    I'm getting this log

    smacdonald2008
    smacdonald2008
    Level 10
    September 26, 2018

    How are you creating your bundle/Java project. Are you following an online doc or using Maven Archetype project?

    Peter_Puzanovs
    Community Advisor
    Peter_PuzanovsCommunity Advisor
    Community Advisor
    September 27, 2018

    Are you working through corporate proxy?

    These things like to intercept POST requests.

    E.g. upload of .jar is blocked and you get 405 as a response.

    Regards,

    Peter

    V
    vineetp40789287Autore
    Level 2
    September 28, 2018

    yes,I'm working in corporate proxy but i tried not using that proxy also.still not working.

    joerghoh
    Adobe Employee
    joerghohAdobe Employee
    Adobe Employee
    September 28, 2018

    * Is this reproducible on your system?

    * do you see that request in the request.log? Or the access.log?

    * something suspicious in the error.log?

    HTTP statuscode 405 "method not allowed" might be thrown by the CSRF filter, but I would doubt that (the webconsole is not covered by Sling filters).

      mikezooz
      mikezooz
      Level 4
      October 1, 2018

      can you switch your port number to 4502 and give a try?

      Akash_Kapoor
      Adobe Employee
      Akash_KapoorAdobe Employee
      Adobe Employee
      October 1, 2018

      Hi vineetp40789287​,

      Can you check "allow empty" field in "Apache Sling Referrer Filter" from host:port/sytem/console/configMgr if already not checked?

      It might help you fix the above exception.

        raj_mandalapu
        raj_mandalapu
        Level 7
        October 1, 2018

        As per logs, the referrer URL is empty might be because of below conditions

        • entered the site URL in browser address bar itself.
        • visited the site by a browser-maintained bookmark.
        • visited the site as first page in the window/tab.
        • switched from a https URL to a http URL.
        • switched from a https URL to a different https URL. (only if it is blocked by referrer metatag on website)
        • has security software installed (antivirus/firewall/etc) which strips the referrer from all requests.
        • is behind a proxy which strips the referrer from all requests.
        • visited the site programmatically (like, curl) without setting the referrer header (searchbots!).

        The temporary purpose you can enable allow empty - not recommended in production

        Are you facing the same issue when you deploy through package manager?

        Termini e CondizioniAccessibility statement

        Loading footer...