Skip to main content

Http Request in .NET Compact Edition ended with "Unable to read data from the transport connection … Unknown error (0x0)"

By
We are leaving in a world that begin to be dominates by smart devices – device2device communication is not something new. Today I would like tack about a problems that we had when we integrated 2 smart devices.
One of the devices expose an HTTP endpoint that can be used to communicate with him. Based on a REST API you can send to him different requests. From our desktops all the communication worked perfectly with this device.
When we imported the client code to a Smart Device Project (special project used to write components for Windows Compact Edition and .NET Compact Framework 3.5) we had a big surprise. Each HTTP request to the first device ended with the following error code:
“Unable to read data from the transport connection … Unknown error (0x0)”
…
at System.Net.HttpWebRequest.finishGetResponse()
at System.Net.HttpWebRequest.GetResponse()…
> The code that generated the error code was:
        public void SetColor(Color color)
        {
            if (color != Color.Red
                && color != Color.Green)
            {
                throw new ArgumentException("Color is not supported", "color");
            }
            try
            {
                byte[] messageContent = UTF8Encoding.UTF8.GetBytes(string.Format(MessageBody,
                    color == Color.Red ? RedCode : GreenCode));
                WebRequest request = WebRequest.Create(new Uri(
                                        string.Format("http://{0}/api/{1}/lights/{2}/state",
                                        ConfigurationManager.AppSettings["hueIP"],
                                        ConfigurationManager.AppSettings["hueUser"],
                                        ConfigurationManager.AppSettings["hueNumber"])));
                request.Method = "Put";
                request.Timeout = 10000;
                request.ContentType = "application/json";
                request.ContentLength = messageContent.Length;
                using (Stream stream = request.GetRequestStream())
                {
                    stream.Write(messageContent, 0, messageContent.Length);
                }
            }
            catch (Exception ex)
            {
                Trace.TraceError(ex.Message);
            }
        }
Because we use HttpWebRequest we expected to have a same a similar behavior with “normal” .NET, but it seems that this is not true. When you are working in “normal” .NET a part of the requests method string is automatically converted to UpperCase. In the moment when a request is made, the request method “Put” is converted to “PUT”. But, in a Smart Device project this is not happening – because of code optimization. So you end up with an HTTP request that has the method set to “Put”.
In general, the system will not have any kind of problems with this, because will know how to handle a request method written CamelCase.  In our case the second smart device it seems that cheeks the request method only with PUT written UpperCase.
In conclusion, when you work with a specific protocol, I recommend to always use the exact specification of the protocol and don’t assume that different stacked will make your job for you.

Comments

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

By
Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...
Post a Comment
Read more

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

By
The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...
Post a Comment
Read more