Need .NET Core YARP Reverse Proxy Setup (Partial Legacy MVC App)

@softsolution2000

I am not polyto. The reason for using YARP in the migration is to seamlessly bridge the partial ASP.NET MVC project with a .NET Core app, ensuring a smooth transition. When proxying legacy MVC pages, I will handle auth/cookies by maintaining stable session behavior to keep the user experience consistent. To run the legacy app + YARP locally and in production, I will set up separate environments for testing and deployment, ensuring a high-level of performance and security. My time estimate for this task is X weeks, and I believe we can discuss the budget once the full project scope is defined. Looking forward to working together on this project to achieve a successful migration. Please go through my profile its 15 years old see the work I did over the years. No Win No Fee means that your satisfaction is my utmost priority. Lets discuss the job details. Moreover, I am willing to start the job and perform tasks without even being hired; it is just to show my commitment to this project. Looking forward to hear from you.

@juanjosec63

I am not polyto Hi, I have strong experience in C#, ASP.NET MVC, .NET Core, YARP, and backend migration work where legacy and modern applications need to run together safely during transition phases. The reason to use YARP here is to create a controlled bridge between the legacy MVC app and the new .NET Core application, so selected routes can move gradually without breaking the existing system or forcing a risky full rewrite upfront. For auth and cookies, I usually keep the legacy app as the source of truth at first, then make sure cookie domain, path, forwarding headers, and proxy behavior are aligned so the user session stays consistent across proxied pages. For local and production setup, I would run the legacy MVC app and YARP as separate services, with YARP sitting in front as the entry point and routing only the selected pages while keeping configuration clean and easy to extend later.

@jeanpatrickr8

I am not polyto. I understand you are looking to migrate a partial ASP.NET MVC project to .NET Core using YARP as a reverse proxy. This transition is critical for maintaining session stability while ensuring that the legacy app's key functionalities are seamlessly integrated into the new environment. With over five years of experience in ASP.NET and .NET Core development, I have successfully executed similar migrations and integrations. My expertise with YARP, along with a strong grasp of authentication and session management, enables me to effectively handle your project requirements. To achieve your goals, my approach will include: - Setting up a .NET Core application using YARP to proxy the specified routes from your legacy app. - Implementing necessary header and path transformations to ensure compatibility. - Configuring session management to maintain consistent authentication across proxied pages. - Providing thorough configuration documentation and handover notes for seamless knowledge transfer. I estimate that this project will take approximately 2 weeks to complete, with a budget of $1,500. I am eager to start and confident in delivering quality results. Please feel free to reach out for further discussions on this project.

@dmytroy7

I am not polyto YARP is useful here because it lets you move traffic route by route from the legacy ASP.NET MVC app to the new .NET Core app without a risky full rewrite. It gives you a controlled bridge for gradual migration, testing, and rollback. For auth and cookies, I usually keep authentication owned by the legacy app first, then make YARP forward the auth cookies and required headers correctly. I also check cookie domain, path, SameSite, secure flags, and machine key/data protection compatibility, because session issues usually come from cookie encryption or mismatched app settings. If needed, I isolate which routes must stay fully on the legacy side to keep behavior stable during this phase. For local setup, I run the legacy MVC app and the YARP app on separate local ports, with YARP as the front door proxying selected routes to legacy. In production, I usually place YARP in front on the main domain and route only selected pages to the old app, while the new .NET Core app serves the rest. This keeps deployment simple and makes migration incremental. I can deliver: a small .NET Core YARP app selected route proxying basic transforms for headers and path rewriting stable cookie/auth handling for proxied pages clean config and short handover notes Estimated time: 2 to 4 days Estimated budget: 200 USD I have experience with migration-style backend work, reverse proxy setup, and debugging auth/session issues, so this validation phase is very realistic. Thank you

@SmartCodeDev

I am not polyto YARP is used here to enable a gradual migration by routing specific requests from the new .NET Core app to the legacy ASP.NET MVC app without rewriting everything at once, reducing risk and downtime. For auth/cookies, I would ensure shared authentication by aligning cookie domains, using the same machine key/data protection (or compatible ticket format), and forwarding auth headers/cookies through YARP so sessions remain valid across both apps. Locally, I would run both apps on different ports with YARP routing to the legacy app; in production, deploy both behind a single entry point (YARP as gateway) with proper domain routing and HTTPS handling. Time estimate: 2–3 days Budget estimate: $150–$250

@ixorawebmob

I am not polyto. I’ve gone through your project details and this is something I can definitely help you with. With over 10 years of experience in web development, including ASP.NET MVC and .NET Core, I am skilled in handling migrations and integrating legacy systems using YARP. My focus is on ensuring clean architecture, scalability, and smooth session handling to maintain your application’s stability. The scope sounds clear, and I can build the required YARP reverse proxy to proxy selected routes/pages from your legacy application, add necessary transforms, and provide comprehensive configuration and handover notes. Here is a brief overview of how I would approach this: 1. YARP is chosen for its flexibility and ease of setup in handling proxying while maintaining session and authentication stability. 2. I handle auth and cookies by ensuring the middleware appropriately manages them, preserving state across requests. 3. For local and production running, I would set up the legacy app and YARP as separate services, managing them through Docker for ease of deployment and scaling. Here is my portfolio: https://www.freelancer.in/u/ixorawebmob I’m interested in your project and would love to clarify any additional details. Looking forward to your response. Regards, Arpit Jaiswal

@chiragpipal

⚠️ If you're not happy, you don’t pay. ⚠️ Hi there, thank you for checking my proposal and sharing the detailed project brief. I can build your YARP app for migrating your partial ASP.NET MVC project to .NET Core seamlessly, ensuring a smooth transition with stable session/auth behavior. I will deliver: • .NET Core YARP app development • Selected route/page proxying • Basic transforms for headers and path rewriting • Stable session/auth behavior on proxied pages • Clean configuration setup and detailed handover notes You will also receive: • Guide on handling auth/cookies during proxy • Support for running legacy app + YARP locally and in production I am confident I can execute your vision professionally and efficiently. Looking forward to discussing timeline and next steps. Best regards, Chirag.

@daxm0

Hello, I’ve reviewed your project, Need .NET Core YARP Reverse Proxy Setup (Partial Legacy MVC App), and I’m genuinely interested. With my experience, I’m confident I can complete it efficiently and to a high standard. I fully understand your goals and the direction of this project. My focus will be on accuracy, quality, and efficiency throughout the process. I am committed to delivering an outcome that meets and exceeds your expectations. With 6 years of experience as a senior software engineer, I’ve worked on a wide range of projects and helped solve many technical challenges. I’m confident I can handle your project and deliver strong results through clear communication and a smooth process. If anything about the requirements isn’t completely clear yet, we can discuss it together and refine the details as we move forward. If you want the best possible outcome, I would be grateful to be considered for this project. I always focus on delivering quality work on time so that the solutions I build help grow your business rather than slow it down. I’d like to clarify your requirements and confirm my understanding through a quick conversation. Once everything is clear, I can get started right away and keep communication smooth, especially with the time zone difference. I’d also appreciate it if you could take a moment to review my profile and feedback. I’m confident I can deliver results that exceed your expectations, and I’m fully ready to get started. best regards, Dax M

@mahads31

Using YARP for the migration of your partial ASP.NET MVC project to a .NET Core app is an excellent choice for maintaining and improving the efficiency of your application. My understanding of both the .NET Framework and .NET Core, paired with my experience with APIs and backend development, makes me particularly well-suited for this task. Having implemented similar migrations in the past, I am well-versed in establishing YARP as a reverse proxy, selecting relevant routes/pages, applying necessary transforms, and preserving session/authentication behavior. When it comes to handling authentication/cookies during proxying on legacy MVC pages, my approach is strategic. I understand the importance of ensuring stability in these aspects to maintain a seamless user experience. Drawing on my proficiency with .NET technologies, I will implement secure mechanisms to ensure that authentication data remains intact through proxy requests, taking into account any path rewriting or header modifications that may be necessary while maintaining your established session behavior.

@KanzahAfaqAhmad

I am not polyto Hello There, I understand you're looking to bridge your partial ASP.NET MVC project with a .NET Core app using YARP as a reverse proxy. Leveraging YARP is an excellent choice because it allows for flexible routing and dynamic configuration. For your project, I'll ensure that the proxying of selected routes along with necessary header/path transformations keeps your session and authentication stable. I am Kanzah Afaq, a skilled developer with over 7 years of experience in .NET, C# Programming, MVC, ASP.NET, and Web Development. I have successfully managed various projects involving backend development and API integrations. Regarding your queries: - YARP helps in managing complex routing needs with minimal changes to existing applications. - I maintain auth and cookie integrity by utilizing proper reverse proxy headers and ensuring consistency in session handling. - Locally, I would run the legacy app alongside YARP using Docker or similar environments, scaling up for production as needed. Estimated budget: $500 Time estimate: 2 weeks I look forward to discussing this further. Thank you, Kanzah Afaq [Portfolio](https://www.freelancer.com/u/KanzahAfaqAhmad)

@mutahrar

I am not polyto Hello, I can build your .NET Core YARP reverse proxy to bridge your existing ASP.NET MVC (.NET Framework) app by setting up a lightweight YARP gateway that selectively routes legacy endpoints into the new Core pipeline while applying necessary path rewrites, header transforms, and preserving session continuity. YARP is ideal here because it provides high-performance, configurable reverse proxying within ASP.NET Core, allowing incremental migration without breaking the legacy system or requiring full immediate rewrite. For authentication/cookies, I would ensure cookie domain/path alignment, enable secure cookie forwarding, and configure YARP transforms to preserve auth headers while handling SameSite and session affinity so the legacy MVC auth flow remains intact across proxied routes. Locally, I would run both apps side-by-side using different ports (IIS Express/Kestrel for MVC and Kestrel for YARP) with reverse proxy routing through localhost; in production, I would deploy YARP as the front-facing gateway on IIS/Kestrel while the legacy MVC app runs as an internal service behind it with restricted direct access. Deliverables include fully working YARP project, route configuration, auth-safe proxy setup, and clean handover notes. Estimated time is 2–3 days a

@ayesha86664

Hi there! I am not polyto. You are bridging an ASP.NET MVC app with .NET Core using YARP and the real challenge is preserving authentication and session flow while routing legacy endpoints safely during incremental migration. I have implemented .NET Core and YARP reverse proxy setups for staged migrations where legacy MVC systems stay fully operational while traffic is gradually shifted through controlled routing layers. This improves stability and reduces migration risk. YARP is used here to enable reverse proxy routing and decouple the legacy MVC app from the new .NET Core layer for step-by-step migration. Auth and cookies are handled by preserving domain scope, forwarding headers, aligning SameSite and Secure flags, and ensuring identity cookies flow consistently across proxied routes. For local setup I run MVC and YARP side by side using Kestrel, and in production YARP sits in front of IIS or containerized services acting as the routing gateway with path rewrite and header transforms. Check our work: https://www.freelancer.com/u/ayesha86664 Is your current authentication based on OWIN cookie auth or a custom session mechanism inside MVC? I am ready to start — just say the word. Best Regards, Ayesha

@AlexVydrin

I am not polyto! I am a full stack developer with experience in legacy system modernization and I can help you validate this migration strategy. Using YARP is the ideal choice for an incremental migration because it allows you to route traffic to the new .NET Core app while transparently proxying unsupported or legacy routes to the old MVC project. This "Strangler Fig" pattern minimizes downtime and risk by letting you move one module at a time. To handle auth and cookies, I would implement shared cookie authentication. This involves configuring both apps to use the same Data Protection keys and cookie names, ensuring that a user logged into the legacy app remains authenticated when YARP proxies them to the new system. For local development, I would run both apps on different ports in IIS Express or Kestrel, with YARP routing traffic based on the configuration. In production, YARP acts as the primary ingress point on a VPS or App Service, forwarding requests to the legacy backend over a private network or internal endpoint. I estimate this technical validation phase will take approximately 15 to 20 hours to ensure auth stability and proper route mapping. My budget estimate for this specific scope is $250.00 USD. I look forward to providing the clean configuration and handover notes you need to move forward with your migration.

@alexnebo1123

Hello, "I am not polyto." YARP is a strong choice for this phase because it lets the new .NET Core app sit in front of the legacy ASP.NET MVC app and route only the selected pages through a controlled gateway. That makes migration safer and more incremental, since routing, rewrites, and compatibility checks can be validated first without rebuilding the whole system at once. For auth and cookies, I keep the legacy behavior intact by forwarding the required headers and cookies carefully, preserving host/path rules where needed, and aligning cookie domain, secure, and same-site settings so proxied MVC pages continue to behave consistently. Locally, I would run the legacy app and the YARP app side by side on separate ports with route-based proxying. In production, I’d place YARP as the front entry point and let it forward only the selected legacy routes while keeping configuration clean and easy to extend during later migration stages. This is a small and practical validation task, and it fits my full-stack background well. For this scope, my estimate is around 1 to 2 days, and the budget would be about $150 to $250 depending on the current state of the partial project and how much session/auth adjustment is needed. Thanks Oleksandr

@ivank69

I am not polyto Hi there, are the proxied pages staying server-rendered inside the legacy MVC app, or do you also need shared auth flow with new .NET Core endpoints? Also, are you using Forms Auth, ASP.NET Identity, or custom cookies in the legacy app right now? YARP is the right choice here because it lets you keep the legacy MVC app running while moving routes gradually into .NET Core without a risky full rewrite. For auth and cookies, the safe approach is to keep one clear cookie domain/path strategy, forward required headers carefully, and avoid breaking session expectations on proxied routes. Locally, I would run legacy MVC and YARP side by side with fixed ports and route mapping. In production, YARP would sit in front and proxy only the selected legacy paths during migration. Handled similar bridge and migration work across old and new stacks. Estimated 2-4 days, budget around $180-$300. Best, Ivan

@ivicab6

I am not polyto. My name is Ivica and with over 6 years in the domain, I am confident in my ability to ace your .NET Core YARP reverse proxy setup. I've been shipping web applications end-to-end throughout my career and this project seems like a perfect staging for my expertise. I've handled projects as unique as yours diligently, even automating business workflows to minimize human intervention, errors and reduce operational time - skills that align well with your need for "clean config + brief handover notes". To address your specific questions, YARP is an ideal choice for this task as it provides a powerful toolset to bridge the gaps between your legacy ASP.NET MVC project and the .NET Core app. I'm adept at handling authentication protocols effectively when proxying legacy MVC pages, ensuring session and cookie stability during migration which is vital for uninterrupted user experience. Running the combined system locally and in production will involve high-level resource utilization. With my profound experience, I'm familiar with deploying such systems efficiently on localhost and productive environments while adhering strictly to industry best practices. My time estimate for this task would be approximately X but more importantly, quality work within stipulated time bounds isn't one bit negotiable for me. Let's overcome the maze together by transforming your legacy partial app into the lean & efficient .NET Core application you envision!

@rishi9343

I am not polyto. While my profile predominantly shows my expertise in mobile app development, I have extensive experience in backend service development and optimization, including using .NET. In ligne with your project, I have the skills needed to build your .NET Core YARP app from scratch. From configuring the environment to creating clean code and providing comprehensive handover notes, I've done it all. In terms of using YARP for this migration, it is an excellent choice for several reasons. YARP simplifies the process of proxying selected routes/pages from your legacy app while maintaining stable session and authentication behavior. This helps ensure a seamless transition between the two apps without causing any interruptions for your users. My proficiency with YARP ensures you receive a smooth, well-integrated solution. Regarding auth/cookies handling when proxying legacy MVC pages, I understand the complexities that may arise during such migrations and can offer effective solutions. I will work on leveraging the power of .NET Core’s authentication middleware to manage and transfer authentications securely between the legacy and YARP services.

@jordanrafael7

Hello, I’ve reviewed your requirement to bridge a legacy ASP.NET MVC (.NET Framework) app with a .NET Core YARP reverse proxy for a migration validation phase. I can set up a clean YARP solution that proxies selected routes while keeping auth/session behavior stable. I am not polyto Answers: 1. Why YARP? YARP enables a strangler-fig migration approach, allowing .NET Core to sit in front of the legacy MVC app and gradually route traffic between old and new systems without downtime. 2. Auth/cookies handling: I would ensure cookie domain/path alignment, forward auth cookies/headers via YARP transforms, and handle SameSite/Secure settings properly to maintain session continuity across proxied pages. 3. Local + production setup: Locally, run both apps side-by-side and configure YARP to route to localhost endpoints. In production, YARP runs as the gateway (IIS/Nginx/Kestrel) routing to legacy IIS app and future services. Approach: Build .NET Core YARP reverse proxy Configure route mappings for selected MVC pages Add path/header transforms Ensure stable session/auth flow Provide clean config + handover notes Estimate: Time: 1–2 days Budget: within $30–250 range I’ve worked on similar YARP strangler-pattern migrations ensuring safe legacy-to-core transitions. Best regards, Jordan Rafael

@amadorjay

I am not polyto. The main challenge is ensuring seamless session management and authentication during the proxying of legacy ASP.NET MVC pages. Another complexity lies in maintaining consistent data flow and state between the legacy application and the .NET Core app while implementing the required path rewrites and header transformations. What considerations will you take into account for maintaining session integrity across the proxy? How will you manage potential discrepancies in authentication mechanisms between the legacy and new applications? What is your strategy for testing the local setup versus production to ensure reliability? I estimate this task will take approximately 20 hours, with a budget of $1,500. Looking forward to discussing the architecture further.