[ 
https://issues.apache.org/jira/browse/HDDS-5828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zita Dombi updated HDDS-5828:
-----------------------------
    Status: Patch Available  (was: In Progress)

> [HTTPFSGW] Add proper handling for unsupported operations
> ---------------------------------------------------------
>
>                 Key: HDDS-5828
>                 URL: https://issues.apache.org/jira/browse/HDDS-5828
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: István Fajth
>            Assignee: Zita Dombi
>            Priority: Major
>              Labels: pull-request-available
>
> As stated in the design doc, we need to address unsupported calls properly in 
> HTTPFS GW. There is a default error handler, that handles queries that are 
> supported by the HDFS NameNode but are not supported by the HDFS HTTPFSGW 
> implementation, we can partly rely on that, but there are some operations 
> that would require extra care.
> Relevant part of the design:
> Handling of unsupported calls
> For calls that we do not have support for in Ozone, HTTP 501 Not Implemented 
> status code has to be returned. As described in 
> [RFC2616|https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html] by the 
> World Wide Web Consortium, this status code is the response to be given when 
> "The server does not support the functionality required to fulfill the 
> request. This is the appropriate response when the server does not recognize 
> the request method and is not capable of supporting it for any resource."
> Handling of invalid operations on volumes or buckets
> For example file creation is not allowed by the ofs scheme on volume and 
> bucket paths, these operations should return an HTTP 400 Bad Request status 
> code, with a proper error message in the response body.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to