Skip to content

Treat 307 and 308 as redirects in HTTPS imports #43679

Description

@kidonng

What is the problem this feature will solve?

Quoting #36328 (comment):

We should probably think of adding support for HTTP status code 307 and 308 at some point.

What is the feature you are proposing to solve the problem?

Per RFC 7231 and 7238, HTTP 307 and 308 status code are also for redirect responses.

What alternatives have you considered?

N/A

Activity

  1. aduh95 commented on Jul 5, 2022

    @aduh95
    Contributor

    Would you like to send a PR to address this?

  2. added
    loadersIssues and PRs related to ES module loaders.
    on Jul 5, 2022
  3. hemanth commented on Jul 6, 2022

    @hemanth
    Contributor

    I came it bit late on this. Does this look good?

  4. LiviaMedeiros commented on Jul 7, 2022

    @LiviaMedeiros
    Member

    @hemanth Yes, your approach also looks good. However, the code is about fetching modules (i.e. importing over network), not about fetch. This makes test changes unrelated to this issue, but they could still be useful as generic test improvement.

  5. hemanth commented on Jul 7, 2022

    @hemanth
    Contributor

    Ah, HTTPS imports. Can we emulate them as well?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestIssues requesting new Node.js features.loadersIssues and PRs related to ES module loaders.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions