This sounds like it may be happening due to this issue:
https://jira.duraspace.org/browse/FCREPO-640
...which was fixed with the Fedora 3.4 release.
In short, if the client came in on a local IPv6 interface, the old
default policies weren't smart enough to recognize that it was the
loopback address ("localhost") in all cases, so it caused the requests
to fail authorization.
- Chris
On Tue, Sep 28, 2010 at 6:20 AM, Carsten Schnober <schno...@elda.org> wrote:
> On 27/09/2010 19:37, Ricardo Borillo wrote:
>
> Hi,
>
>> I just check that all works fine if i access with 127.0.0.1 instead
>> of localhost ...
>>
>> Is this normal?
>
> Having had the same problem, I think that this is normal indeed. The
> XAMCL default configuration denies any access from a remote host.
> In order to change that, I removed the file
> deny-apim-if-not-localhost.xml from the directory
> fedora/server/fedora-internal-use/fedora-internal-use-repository-policies-approximating-2.0.
> However, the 'clean' (and secure) way would be to adapt it according to
> your needs, I suppose.
> Regards,
> Carsten
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Fedora-commons-users mailing list
> Fedora-commons-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
>
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Fedora-commons-users mailing list
Fedora-commons-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
