


vineetp40789287
vineetp40789287
24-09-2018
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.
smacdonald2008
smacdonald2008
24-09-2018
Its hard for commnity to suggest a fix without more information. Please post any log messages that you are seeing
vineetp40789287
vineetp40789287
24-09-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
26-09-2018
How are you creating your bundle/Java project. Are you following an online doc or using Maven Archetype project?
vineetp40789287
vineetp40789287
26-09-2018
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
smacdonald2008
27-09-2018
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.
PuzanovsP
MVP
PuzanovsP
MVP
27-09-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
vineetp40789287
vineetp40789287
28-09-2018
yes,I'm working in corporate proxy but i tried not using that proxy also.still not working.
vineetp40789287
vineetp40789287
28-09-2018
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.
Jörg_Hoh
Employee
Jörg_Hoh
Employee
28-09-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).