Sorry for the late reply.
If that's the case, please jump into dev@marmotta, so we can address the
issue authorizing PATCH requests.
Thanks!
On Fri, Mar 8, 2019, 05:09 Alan Snyder wrote:
> I got it working! I had to enable PATCH in the security module for all
> update methods - I'll figure out
I got it working! I had to enable PATCH in the security module for all
update methods - I'll figure out exactly which one is the single necessary
one to allow this, but the PATCH mechanism does work against my container,
and I can test it!
On Thu, Mar 7, 2019 at 10:22 AM Alan Snyder wrote:
> G
Got *quiet* :)
On Thu, Mar 7, 2019 at 10:18 AM Alan Snyder wrote:
> Got quite lately... :)
>
> Any thoughts on this?
>
> On Sun, Mar 3, 2019 at 7:32 PM Alan Snyder wrote:
>
>> update on this - looking at the curl ascii trace, I'm getting a 401 back
>> from Marmotta...
>>
>> < HTTP/1.1 401 Unaut
Got quite lately... :)
Any thoughts on this?
On Sun, Mar 3, 2019 at 7:32 PM Alan Snyder wrote:
> update on this - looking at the curl ascii trace, I'm getting a 401 back
> from Marmotta...
>
> < HTTP/1.1 401 Unauthorized
>
> HTTP/1.1 401 Unauthorized
>
> < Server: Apache-Coyote/1.1
>
> Server:
update on this - looking at the curl ascii trace, I'm getting a 401 back
from Marmotta...
< HTTP/1.1 401 Unauthorized
HTTP/1.1 401 Unauthorized
< Server: Apache-Coyote/1.1
Server: Apache-Coyote/1.1
* Authentication problem. Ignoring this.
< WWW-Authenticate: Basic realm="Apache Marmotta"
WWW
