# Turbolinks-Location and Turbolinks-Referrer headers equivalent **URL:** \ **Category:** General\ **Created:** [December 25, 2020, 12:07am UTC](https://discuss.hotwired.dev/t/turbolinks-location-and-turbolinks-referrer-headers-equivalent/1662 "2020-12-25T00:07:45Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![ssa3512](https://yyz1.discourse-cdn.com/flex027/user_avatar/discuss.hotwired.dev/ssa3512/32/1180_2.png) [@ssa3512](https://discuss.hotwired.dev/u/ssa3512)\ **Post date:** [December 25, 2020, 12:07am UTC](https://discuss.hotwired.dev/t/turbolinks-location-and-turbolinks-referrer-headers-equivalent/1662/1 "2020-12-25T00:07:45Z")
I am attempting to port an example [ASP.NET](http://ASP.NET) core backend from Turbolinks to Hotwire. ([https://github.com/khalidabuhakmeh/turbolinks.net](https://github.com/khalidabuhakmeh/turbolinks.net)) The implementation makes use of the Turbolinks-Referrer HTTP header to identify turbo requests and attaches a Turbolinks-Location to the result. I am not seeing anything equivalent to these headers in the Turbo Drive library. Is the use of these headers necessary at all, or can they be dropped when migrating to the new Turbo? ---
**Author:** ![sam](https://yyz1.discourse-cdn.com/flex027/user_avatar/discuss.hotwired.dev/sam/32/1091_2.png) [@sam](https://discuss.hotwired.dev/u/sam)\ **Post date:** [December 25, 2020, 12:44am UTC](https://discuss.hotwired.dev/t/turbolinks-location-and-turbolinks-referrer-headers-equivalent/1662/2 "2020-12-25T00:44:43Z")
No need for those headers anymore. Turbo uses fetch instead of XHR which lets us detect and follow redirects without any special server-side work. ---
**Author:** ![mickdelaney](https://yyz1.discourse-cdn.com/flex027/user_avatar/discuss.hotwired.dev/mickdelaney/32/1332_2.png) [@mickdelaney](https://discuss.hotwired.dev/u/mickdelaney)\ **Post date:** [January 7, 2021, 7:45am UTC](https://discuss.hotwired.dev/t/turbolinks-location-and-turbolinks-referrer-headers-equivalent/1662/3 "2021-01-07T07:45:42Z")
@ssa3512 are you working in an open repo ? Would like to help out. ---
**Author:** ![ssa3512](https://yyz1.discourse-cdn.com/flex027/user_avatar/discuss.hotwired.dev/ssa3512/32/1180_2.png) [@ssa3512](https://discuss.hotwired.dev/u/ssa3512)\ **Post date:** [January 8, 2021, 9:42pm UTC](https://discuss.hotwired.dev/t/turbolinks-location-and-turbolinks-referrer-headers-equivalent/1662/4 "2021-01-08T21:42:50Z")
@mickdelaney not really right now - I was using the project I linked as a starting point but haven’t had a lot of time to look at since I posted. It does seem that most of the server side code for turbolinks is just not necessary anymore. One thing that would be definitely be interesting would be to try and get turbo streams working using SignalR but I just haven’t had time. ---
**Author:** ![AdamLuczynski](https://yyz1.discourse-cdn.com/flex027/user_avatar/discuss.hotwired.dev/adamluczynski/32/1510_2.png) [@AdamLuczynski](https://discuss.hotwired.dev/u/AdamLuczynski)\ **Post date:** [February 18, 2021, 12:55pm UTC](https://discuss.hotwired.dev/t/turbolinks-location-and-turbolinks-referrer-headers-equivalent/1662/5 "2021-02-18T12:55:01Z")
Do you have any idea how to render partial as `` ? ---
**Author:** ![m2017atTR](https://yyz1.discourse-cdn.com/flex027/user_avatar/discuss.hotwired.dev/m2017attr/32/4106_2.png) [@m2017atTR](https://discuss.hotwired.dev/u/m2017atTR)\ **Post date:** [May 20, 2025, 1:02am UTC](https://discuss.hotwired.dev/t/turbolinks-location-and-turbolinks-referrer-headers-equivalent/1662/6 "2025-05-20T01:02:07Z")
Sad to hear… I am working on to find a solution using turbo frames (like turbolink) main purpose using old school controller \> view and not to use SignalR or WebScokets. Sockets are nice but really not want to use it.