•  
      request #9230 Artifact API doesn't follow RFC
    Infos
    #9230
    Manuel Vacelet (vaceletm)
    2016-08-09 14:29
    2016-06-07 14:30
    9513
    Details
    Artifact API doesn't follow RFC

    And this might break some reverse proxy:

    • The "Last-Modified" header is sent with ISO8601 format while RFC1123 is a MUST according to https://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.3.1. This breaks Apache 2.4 + FastCGI / php-fpm that goes nuts with last-modified not RFC compliant.
    • The return code for POST /artifacts/ returns 302, whereas it should be 201 according to https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html. This breaks nginx18 + FastCGI / php-fpm + guzzle for tests that goes nuts because there is a redirect after a POST
    • The "Location:" header is used to redirect according to https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.30. This is a problem as it's systematicaly used by GET /artifact/:id (ie we force a redirect that is not necessary). In worst cases, that might lead to infinite loops
    API
    8.15
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2016-06-27
    Attachments
    Empty
    References

    Follow-ups

    User avatar
    Integrated into Tuleap 8.16.99.9

    • Status changed from Under review to Closed
    • Close date set to 2016-06-27