[{"data":1,"prerenderedAt":58},["ShallowReactive",2],{"/2025/10/05-unc-and-url":3},{"id":4,"title":5,"body":6,"date":49,"description":46,"extension":50,"meta":51,"navigation":52,"path":53,"robots":54,"seo":55,"stem":56,"__hash__":57},"posts/2025/10/05 UNC-and-URL.md","05 UNC And URL",{"type":7,"value":8,"toc":45},"minimark",[9,18,25,28,40,42],[10,11,13],"post-title",{":date":12},"date",[14,15,17],"h1",{"id":16},"unc-and-url","UNC and URL",[19,20,21],"notes",{},[22,23,24],"p",{},"This is a repost from my old blog. First posted in 10/10/2018.",[26,27],"br",{},[22,29,30,31,39],{},"Found something weird today. For a long time, we have published our project to the test environment using the following UNC pattern: ",[32,33,38],"code",{"className":34},[35,36,37],"bg-gray-200","p-2","rounded","\\\\testservername.productiondomain.com\\shared-path",". However, when I did that today, it accidentally connected to production.",[26,41],{},[22,43,44],{},"Removing the domain as part of the UNC solves the problem. The weird thing is the same UNC points to our test environment when run on my coworker's computer. Nothing is weird on our hosts file. I have not figured out why this is so.",{"title":46,"searchDepth":47,"depth":47,"links":48},"",2,[],"2025-10-05T00:00:00.000Z","md",{},true,"/2025/10/05-unc-and-url",null,{"title":5,"description":46},"2025/10/05 UNC-and-URL","8vvCG9negtnsogildfusvgShOh5fRNGG0_czanAnjH4",1785167452973]