Hi Blazas, can it be by any chance the Referrer filter introduced in [0]?
Regards Antonio [0] https://issues.apache.org/jira/browse/SLING-2141 On Dec 21, 2011, at 3:59 PM, Balazs Toth wrote: > Hi Sam, > > thanks for your time, you got me in the right direction even though the > problem lies in our own codebase and not in Sling :) I am still new to Apache > Sling so sometimes I blame it for errors it is not responsible for :) > > Balazs > > > On Dec 21, 2011, at 3:35 PM, sam ” wrote: > >> How did you login to the repository? >> How did you send POST request? >> >> I cannot grep for Blacklist in sling trunk. >> >> >> On Wed, Dec 21, 2011 at 9:02 AM, Balazs Toth <[email protected]> wrote: >> >>> Hi, >>> >>> by accessing a node in my local repository (POSTing to it) I get the >>> following response from the Sling instance: >>> >>> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >>> <html> >>> <head> >>> <title>403 Blacklisted address 127.0.0.1</title> >>> </head> >>> <body> >>> <h1>Blacklisted address 127.0.0.1 (403)</h1> >>> <p>The requested URL >>> /demo/content/form_0cc535c1-d483-4a23-8ab6-6299c256f53f/form-text-element_2 >>> resulted in an error in Sling Default Error Handler Servlet.</p> >>> <hr> >>> <address>ApacheSling/2.0 (Java HotSpot(TM) 64-Bit Server VM 1.6.0_29; Mac >>> OS X 10.6.8 x86_64)</address> >>> </body> >>> </html> >>> >>> Seemingly localhost is blacklisted by some reason and I cannot figure out >>> how could it be removed from the blacklist, or even where this blacklist >>> even exists. The problem came out of nowhere, I cannot reproduce its >>> triggering event. I would gladly welcome any ideas in the matter. Thank you! >>> >>> Balazs >>> >>> >
