Further, the beacon itself had not been reassembled correctly as at least one of the o-ring seals was pinched sideways instead of being seated around the screw. Also, upon arrival I found that it had not been repacked in the foam correctly and one of the plastic screws on the practice beacon had been bumping against the recharger and broke off. They shipped it in just the Pelican case without a box or lock, which did not make me too happy, but whatever. I checked with Wing, gave them my Credit Card and waited for it to come back. I pointed out that this had been a DOA failure and we should not have to pay for their labor, but since we had sat on this for two years (their records indicate it was delivered in 2006!), it was reasonable to pay for the parts and shipping ($40). At first, Corbham wanted me to pay for the part, labor, and return shipping to the tune of about $120. The issue was a $5 switch that needed to be replaced. While its now repaired and appears fully functional, I'm still disappointed, if only because my expectations were so high. Like, I didn't notice their influence, but maybe we do need to prefix the "not found" properties as well? I leave it to your appreciation before starting to update the tests accordingly.After all the above (and more external from CT), I finally got it back last week - it showed up on Tuesday at 1030, and I had an actual I could use it on that night, so pretty good from a testing perspective. But of course I might be missing some piece of the story, or some detail. I've just updated the CL (patchset 2) with what I found to be the minimum for things to appear working. You don't get any error message, and the window seems to display the network location, but you don't get any contents displayed, because none of the props are prefixed. ![]() So for example, if you prefix only multistatus, href and propstat in the response, which gives you something like that: I've just tried "enabling" prefixes one by one, and the conclusion seems to be that MinRedir simply ignores anything that isn't prefixed. a way that would not change the xml tags of the structs) ? What if we didn't touch xml.go at all, and instead try to do some prepending on the fly everywhere, like I did in prop.go and webdav.go ? But maybe there's another/better way to prefix the XML elements than what I did (i.e. With the approach I took it would be very impractical, since we would have to duplicate the structs types and use one or the other depending on what the client is. Regarding the wobblyness, that was partly the sense of my question in the CL commit msg: do you think we could only prefix the tags when we detect the user-agent matches a "faulty" MiniRedir? That way, not only do we emit "cleaner" XML in the general case, but we also wouldn't have to fix as many tests we could just add a propfind test specific to the faulty MiniRedir case. It's a pain we don't have an exact doc of what MiniRedir wants :/ I'll try and do a more systematic probing of that. I think I actually went the other way around when I tested, and when I had the multistatus, propstat and props already prefixed, but not the top ones in Response (such as href) yet, it was still not working. ![]() I don't know for sure which ones it needs, but I'm almost sure it's more than just the multistatus one. ![]() ![]() Yeah, I had noticed that I had missed the lockentry and co. Here's what happens when trying to connect: I believe the problem is related to what is described at:Īnd indeed, with the change at, there's no problem anymore connecting with Ah right, I hadn't understood what you meant about a litmus server in the CL. Which shows the client is Microsoft-WebDAV-MiniRedir/. The connection does show up server-side, with a PROPFIND request such as:ġ 23:02:02 WEBDAV: &, ERROR: Go version devel +b0532a9 Mon Jun 8 05:13:15 2015 +0000 linux/amd64Īnd /x/net/wedav at dfcbca9c45aeabb8971affa4f76b2d40f6f72328įrom a windows 7 sp1 explorer window, trying to connect at shows a connection error window, with unspecified error 0x80004005
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |