Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

HTTP 405 Error

vineetp40789287
Level 2
Level 2

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.

12 Replies
smacdonald2008
Level 10
Level 10

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

vineetp40789287
Level 2
Level 2

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

I'm getting this log

smacdonald2008
Level 10
Level 10

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

vineetp40789287
Level 2
Level 2

I'm using maven Archetype project . I  have approx 8 bundles to upload , on too many attempts some of the bundles which are hardly of under 100 KB size getting uploaded (that also after several repeated attempts). but others are giving this error.

smacdonald2008
Level 10
Level 10

Last thing - can you try to update same project on a fresh AEM install - this will tell us if the issue is your project or the AEM instance. If you project contains valid OSGi bundles - they should be able to upload it and put them into an Active state.

vineetp40789287
Level 2
Level 2

I have already tried that , even some of the team members are getting the same error in their system  .But at the same time its working in some system.

Peter_Puzanovs
Community Advisor
Community Advisor

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

vineetp40789287
Level 2
Level 2

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

Jörg_Hoh
Employee
Employee

* 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).

michaelvino86
Level 4
Level 4

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

Akash_Kapoor
Employee
Employee

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
Community Advisor
Community Advisor

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?