# Call to netlify function with port 443 in url leads to redirect response

**URL:** <https://answers.netlify.com/t/call-to-netlify-function-with-port-443-in-url-leads-to-redirect-response/86732>\
**Category:** Support\
**Tags:** lambda-functions\
**Created:** [March 1, 2023, 7:49pm UTC](https://answers.netlify.com/t/call-to-netlify-function-with-port-443-in-url-leads-to-redirect-response/86732 "2023-03-01T19:49:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Agiulian](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Agiulian](https://answers.netlify.com/u/Agiulian)\
**Post date:** [March 1, 2023, 7:49pm UTC](https://answers.netlify.com/t/call-to-netlify-function-with-port-443-in-url-leads-to-redirect-response/86732/1 "2023-03-01T19:49:22Z")

</div>

Hello,

I have an issue with my netlify function confirmPayment on my [https://concavegrinder.netlify.app/](https://concavegrinder.netlify.app/) website.

When the function is called it is always called as [https://concavegrinder.netlify.app:443/.netlify](https://concavegrinder.netlify.app:443/.netlify) …  
with the port in the url, I can’t control the way it is called since it’s a foreign service.

This service awaits a confirmation response from the function and it tells me that the response it gets is `Redirecting to https://www.concavegrinder.com/.netlify/functions/confirmPayment` is there any way to avoid this redirects ? Maybe with another request method ? Right now it is called as a POST how can I prevent the service from getting this redirects as a response ?

---

<div class="post-metadata">

**Author:** ![SamO](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/samo/32/41847_2.png) [@SamO](https://answers.netlify.com/u/SamO)\
**Post date:** [March 3, 2023, 8:48pm UTC](https://answers.netlify.com/t/call-to-netlify-function-with-port-443-in-url-leads-to-redirect-response/86732/2 "2023-03-03T20:48:42Z")

</div>

hi there, before we dig in, did you see this brand new guide on debugging redirects?

I strongly suggest you give it a thorough read through and see if this fixes your problem:

> [@\[Support Guide\] Making redirects work for you - troubleshooting and debugging](https://answers.netlify.com/t/support-guide-making-redirects-work-for-you-troubleshooting-and-debugging/13433):
>
> Last reviewed by Netlify Support in July 2025 Introduction You’ve put blood, sweat and tears into building an incredible static site with all the bells and whistles. However, you’ve configured some redirect rules and you’ve come unstuck… they don’t appear to be working! Ensure you’ve followed the correct guidance Our [redirects and rewrites document](https://docs.netlify.com/routing/redirects/) covers a broad range of use cases, from [status codes](https://docs.netlify.com/routing/redirects/redirect-options/#http-status-codes) to [proxying another service](https://docs.netlify.com/routing/redirects/rewrites-proxies/#proxy-to-another-service) and everything in between. Ensure you’re using the correct syntax …

if not, please post again, and we’ll try and troubleshoot.

---

<div class="post-metadata">

**Author:** ![Agiulian](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Agiulian](https://answers.netlify.com/u/Agiulian)\
**Post date:** [March 6, 2023, 9:40am UTC](https://answers.netlify.com/t/call-to-netlify-function-with-port-443-in-url-leads-to-redirect-response/86732/3 "2023-03-06T09:40:49Z")

</div>

Hello, thanks a lot for your response I indeed read this guide on another project, I tried adding a redirect myself on this website to see if I could fix the problem but it didn’t work.

My issue is that the url:port request redirects to url without port before responding and that the service which is calling this url that way catches the redirect as a wrong response.

---

<div class="post-metadata">

**Author:** ![fool](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/fool/32/37_2.png) [@fool](https://answers.netlify.com/u/fool)\
**Post date:** [March 7, 2023, 12:34am UTC](https://answers.netlify.com/t/call-to-netlify-function-with-port-443-in-url-leads-to-redirect-response/86732/4 "2023-03-07T00:34:52Z")

</div>

If your remote service insists on calling us in that weird way, with the port number, I suppose you can insist that they handle the 301 redirect we return.

The better solution would of course be to have them change to calling us without the port number, though it sounds like their service is not flexible enough to do this, so hopefully they can add support for the very standard 301 redirect instead 🙂