Skip to main content

Tuleap Community Edition development and releases are no longer public. You have until September 30th to download packages and sources in Tuleap project. You can contact the team if you need further assistance.

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #9230 Artifact API doesn't follow RFC
    Infos
    #9230
    Manuel Vacelet (vaceletm)
    2016-08-09 14:29
    2016-06-07 14:30
    9517
    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
    Referencing request #9230

    Artifact

    story #8206 Work with "values by field" for GET and POST on /artifacts/:id
    rel #9210 8.17
    Display settings

    Follow-ups

    User avatar
    Nicolas Terray (nterray)2016-06-27 14:10
    Integrated into Tuleap 8.16.99.9
    • Status changed from Under review to Closed
    • Close date set to 2016-06-27