dabla opened a new issue, #45237:
URL: https://github.com/apache/airflow/issues/45237

   ### Apache Airflow version
   
   2.10.4
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   I wanted to raise an AirflowSkipException if a HTTP 404 is returned by a 
REST endpoint if the requested resource isn't found
   
   ### What you think should happen instead?
   
   I would have expected the custom response_check code being invoked, but it 
isn't, as the response status_code is already checked within the check_response 
method of the HttpHook.  There, when the status_code isn't within the 2x or 3x 
range, an AirflowException is being raised, thus making the possibility to 
check the response yourself through a custom response_check obsolete, as the 
code will never be invoked.  A possible solution would be to pass the custom 
response_check defined int the operator to the HttpHook, that way the same 
logic would be applied.
   
   ### How to reproduce
   
   Just define a custom response_check which ignores a 404 and run the 
HttpOperator for a non existing resource which will return a 404, you'll see 
that the custom response_check will never be invoked and the task will fail.
   
   ### Operating System
   
   RedHat
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-http 5.0.0
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to