LTI Proxy Error

[joseph3]

My University's security team appears to have made some firewall changes that impact my  development server.  Any applications that are supposed to load in a Canvas frame fail with a proxy error.  I can get them to work from my production server or localhost running off of my desktop, but not the development environment.  I was told that I need to make a request to security with source, destination, and port information.  I would assume that the source is the URL for our canvas test instance, and the destination is my development server address. Does anyone know of a specific port that I need to request?

Regards,
Joseph Loiacono
Florida Atlantic University

[svickers2]

LTI will just use the same HTTP/S port as your server, this would normally be 443 for https.  HTH.

[dtod]

Perhaps an issue with the referrer policy. I know that Canvas by default uses 

strict-origin-when-cross-origin

and perhaps your proxy is set the same way.

[Semivies]

I see it's been a while since you've posted, but I just want to ask if anyone's run into this issue recently with LTI 1.3? I'm trying to debug something similar and wondering if the proxy config behavior has changed after any Canvas updates. Also curious how folks are testing these tool setups locally—any tips for localhost callback handling?