Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Issues

Select view

Select search mode

 
4 of 4

CFHTTP - Following 301 Redirect results in 403 error

Description

CFHTTP appears to incorrectly follow 301 redirects using this URL: https://resize.lockedoncloud.com/lovii-w:1500-h:1000-q:100/b5/07/70/c8/2b/e1/4f/82/ba/53/e9/28/43/fc/18/c5.jpg

CFHTTP will report a 403 error.

Browsers, Axios and Adobe CF all follow the redirect correctly, and return a 200 status code.

Example:

If you use the CFHTTP option redirect = false, the status code is correctly reported as 301, and the location header as: https://lovii.s3.ap-southeast-2.amazonaws.com/lovii-w%3A1500-h%3A1000-q%3A100/b5/07/70/c8/2b/e1/4f/82/ba/53/e9/28/43/fc/18/c5.jpg, but this is wrong.

Adobe CF 2021, browsers, NodeJs all return the location header correctly as: https://lovii.s3.ap-southeast-2.amazonaws.com/resize/h:1000-q:100-w:1500/b5/07/70/c8/2b/e1/4f/82/ba/53/e9/28/43/fc/18/c5.jpg

Hmm??

Environment

None

Details

Assignee

Reporter

Priority

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Parent

Affects versions

Created 19 April 2023 at 01:39
Updated 30 November 2024 at 13:13

Activity

Show:

Pothys - MitrahSoft19 April 2023 at 12:15
Edited

I checked this issue with the code mentioned above and confirmed the issue with Lucee 6.0.0.377-SNAPSHOT.
Both Lucee and ACF return the 301 statuscode when using CFHTTP with the redirect=false attribute.
But the response header location returns the invalid URL in lucee and ACF returns correct URL.

Flag notifications