• 0

[C#] Am I missing a pitfall with base64 encode sending?


Question

I am always learning different parts of the C# language b/c lets face it, it's a lot of fun :). I've decided to configure my wcf service as a rest service which supports json request/response instead of xml. All has gone well and I can serialize/deserialize my messages into complex classes so far, unless I send a bunch of data in them. I've tried to change my readerQuotas, etc, etc but everytime I try to make a call it says "Error: Bad Data". I know the service works because I can call simple functions and pass data to/from the service. But if I pass a class with 3 byte[] properties each 128 bytes in length it fails. If I pass the same class with each byte[] param with 3 bytes of data it goes through (I base64 encode each complex class after serializing them). Here is my example code:

This example passes and goes through:

GetTestSalesRequest req = new GetTestSalesRequest()
			{
				CurrentTest = new byte[] { 1 },
				CurrentMTest = new byte[] { 4 },
				UserName = this.gl_userName,// <---- is a string
				UserPwd = new byte[] { 2 }
			};

string test = await this.gl_client2.TestFunc(req);
			System.Diagnostics.Debug.WriteLine("Testtion: {0}", test);

This example fails.

GetTestSalesRequest req = new GetTestSalesRequest()
			{
				CurrentTest = CryptographicEngine.Encrypt(keySvr, Encoding.UTF8.GetBytes(test1.ToString()).AsBuffer(), null).ToArray(), // <---- is a byte[]
				CurrentMTest = CryptographicEngine.Encrypt(keySvr, Encoding.UTF8.GetBytes(test2.ToString()).AsBuffer(), null).ToArray(), //<---- is a  byte[]
				UserName = this.gl_userName,// <---- is a string
				UserPwd = this.gl_userPwd // <--- is a byte[]
			};

string test = await this.gl_client2.TestFunc(req);
			System.Diagnostics.Debug.WriteLine("Testtion: {0}", test);

public async Task<string> TestFunc(GetTestSalesRequest request)
		{

string resBody = null;
			byte[] testStr = Encoding.UTF8.GetBytes(WebHelperClass.SerializeJSONObj<GetTestSalesRequest>(request));
			string addr = string.Format("{0}/TestFunc/{1}", this.gl_baseAddr, Convert.ToBase64String(testStr));
			WebRequest req = WebRequest.Create(addr);
			HttpWebResponse res = await req.GetResponseAsync() as HttpWebResponse;
			if (res.StatusCode == HttpStatusCode.OK)
			{
				using (Stream stream = res.GetResponseStream())
				{
					using (StreamReader sr = new StreamReader(stream))
					{
						resBody = sr.ReadToEnd();
						sr.Dispose();
					}
				}
			}
			return resBody;
}

Is there a pitfall I'm going into here? What am I missing that is really obvious because this has to be possible to be done.

10 answers to this question

Recommended Posts

  • 0

Not really strong with debugging other peoples code.. But.. have you tried:

1) Sending the same data but un-encrypted

2) Using AsciiEncoding.Ascii instead of Encoding.UTF8 for the base64 encode?

3) It looks like you are just using the CryptographicEngine, that won't base64 it, have you tried just a plain-jane base64 encode?

4) You pass in a few variables, are you sure they are all initialized correctly?

  • 0

Well basically I'm just taking the json string (that was created by serializing the complex class) in TestFunc and base64 encoding it to send it across to the rest service so I don't have a long query string similar to /TestFunc/{[80,10,01,01,30,10,10], "test":"etc"}. So I am base64 encoding the whole thing then decoding it on the rest service side. If I send the class with only have small amounts of byte data it goes through just fine. If I send each byte[] with having 128 different indexes each then it fails. Ingramator which files do you want? The debugger just outputs saying "The remote server returned an error: (400) Bad Request."

System.Net.WebException was unhandled by user code

HResult=-2146233079

Message=The remote server returned an error: (400) Bad Request.

Source=System

StackTrace:

at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)

at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()

at TestSaleStoreApp.TestSaleRestSvcClient.<TestFunc>d__a.MoveNext() in c:\Users\User\Documents\Visual Studio 2012\Projects\TestSaleStoreApp\TestSaleStoreApp\TestSaleRestSvcClient.cs:line 50

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()

at TestSaleStoreApp.MainUserPg.<initSettings>d__16.MoveNext() in c:\Users\User\Documents\Visual Studio 2012\Projects\TestSaleStoreApp\TestSaleStoreApp\MainUserPg.xaml.cs:line 524

InnerException:

If you need more info let me know :) I'm stumped on this one. As for the ASCII I haven't tried that yet I'll look into it later today but I'm suspecting it has to do with the length of the content (which I've changed the readerQuota settings).

I also really appreciate the help so far guys!

  • 0

It's quite possible you're just sending too much data via the query string, why aren't you just sending it as the request body instead?

base64 makes the content larger, and you don't need to do it with text (like JSON).

  • 0

@The_Decryptor b/c I'm new to using Rest services I'm used to using SOAP :) I'll look into that thanks.

EDIT: My url looks like this:

localhost:8733/Design_Time_Addresses/TestSaleRestSvc/Service1/TestFunc/eyJDdXJyZW50Q29vcmRzTGF0IjpbMiwzLDRdLCJDdXJyZW50Q29vcmRzTG9uZyI6WzMsNCw1XSwiVXNlck5hbWUiOiJyeWFuIiwiVXNlclB3ZCI6WzFdfQ==&pwdKey=Aw==&latKey=JbU2hfwNBi1vHZxH5OnUcKabsT1kx16jqn3BAxLDXPTCHbyIlDyPOoK0NNQVSLmaOD5x1bjzipTM9VJOaQgTIgjmqNtX+l9Jq2EeetSQI58RhCwUFRQGOpKaLEJ03JeZ5UjD3rTzm2HFr5P0SvQBYBsgLB9W1je3PPoD28Ro7IU=&longKey=AQ=="]localhost:8733/Design_Time_Addresses/TestSaleRestSvc/Service1/TestFunc/eyJDdXJyZW50Q29vcmRzTGF0IjpbMiwzLDRdLCJDdXJyZW50Q29vcmRzTG9uZyI6WzMsNCw1XSwiVXNlck5hbWUiOiJyeWFuIiwiVXNlclB3ZCI6WzFdfQ==&pwdKey=Aw==&latKey=JbU2hfwNBi1vHZxH5OnUcKabsT1kx16jqn3BAxLDXPTCHbyIlDyPOoK0NNQVSLmaOD5x1bjzipTM9VJOaQgTIgjmqNtX+l9Jq2EeetSQI58RhCwUFRQGOpKaLEJ03JeZ5UjD3rTzm2HFr5P0SvQBYBsgLB9W1je3PPoD28Ro7IU=&longKey=AQ==

  • 0

Hmm it's always to debug without having it in front of you but I can try and point you in the right direction! :) If its working with smaller data samples it may be that you're [trying to encode an unsupported data type]/[base64 doesn't know what to encode so its sending invalid data] but I can't tell from the log there. The most common problem I find is that the data buffer is not being completely filled or filled correctly so I'd investigate that first! Enable tracing first, instructions here http://msdn.microsoft.com/en-us/library/ms733025.aspx :p then test and it will show you exactly where the problem is occurring. Hope this helps, good luck with the project mate!

  • 0

Writing the object to the body stream and changing the parameter type of the service to the complex object instead of a string made it work for some reason. REST is more of a pain learning how to use then SOAP that is for sure :)

  • 0

So I want to take this time to thank everyone who helped me. You guys are all great assets to this community and I hope I can give back one day by finding other questions I can answer in this forum and post my 2 cents on the subject (you guys are just too quick it seems most of the time and say what I would say :) ). +1 to you all and I hope you have a good holiday.

This topic is now closed to further replies.
  • Posts

    • Tesla instructor reportedly said staff leave with a 'negative taste in their mouth' by Hamid Ganji Tesla has been making the headlines over the past few months due to Elon Musk's controversy in the Department of Government Efficiency, aka DOGE. People have been marching to the streets, boycotting Tesla, and even setting their already-bought Tesla cars on fire. Tesla temporarily shut down its factory in Austin for the week of Memorial Day, and employees could either take paid time off or attend a series of training sessions. Business Insider now claims to have obtained a recording of the sessions that reveals some interesting details about the Tesla culture and how its employees feel about the company. The Tesla instructor reportedly asked employees to respond if they ever felt "I can't work under these conditions" and were uneasy about the company's constant change. "I know I have," the instructor said. "A lot of people leave this company, and they have kind of a negative taste in their mouth," the Tesla instructor added. "They think: 'Man, it was terrible. It was bad. I got burnt out. I feel like I didn't get anything done, nobody listened to me.'" Hundreds of Tesla employees allegedly attended the meetings, where they were asked to take more responsibility for improving the company's culture. "Leadership has kind of another level of responsibility for trying to guide and direct that culture," the instructor told Tesla staff. "But at the end of the day, it's us as the people on the ground that are the reflection of the culture." Tesla's factory in Austin produces Cybertruck and Model Y. The staff said shutting down the factory for the sake of Memorial Day has been unusual for the company. Elon Musk recently announced that he would leave his position at the White House and added that he'll remain Tesla CEO for another five years. In the meantime, the latest data shows Tesla sales in Europe have dropped 49 percent, and the company's profit in Q1 2025 declined by 71 percent.
    • More like you took offense to the letdown and I find it hilarious. Most people aren’t reading tech blogs, and for those that do, they know what the difference is. So really it’s a non-story to YOU, because you don’t like what it says.🎻
    • Building 100 hospitals around the world would have spent his fortune easily. But that would not keep him at the table with the elites in the world for the rest of his life. Or keep him from chanting about how good he is to the poor people around the globe to the media.
    • Exactly. that's what I use when I do use Windows 10 on my Linux through QEMU/KVM VM (the 'activation' is tied to the UUID of the VM) and, like you said, that Jan 2032 version of Win10, even if decent program/game support ends earlier than Jan 2032, I suspect, for a conservative figure, that we got at least 2-3 years from now (so call it 2027-2028) before Win10 may start to become more of a legitimate issue. but for general usage I suspect we got a 'easy' 2-3+ years. because like you say, as long as browsers don't start to become a issue, all the more reason to continue using Win10 for many, probably most, people. even when it comes to browsers, you mentioned Firefox supports Win7 until end of August etc... but I think it's just ESR releases which, while I get it technically works, are when browser support is getting a bit long-in-the-tooth. but as long as the standard Firefox release is still supported, then one is still easily well within the 'good support range', which my comment basically plays inline with what Werct said, which I suspect comes back to my 2027-2028 estimate before Win10 'starts' to legitimately fade off into the sunset
  • Recent Achievements

    • Dedicated
      jbatch earned a badge
      Dedicated
    • Week One Done
      Leonard grant earned a badge
      Week One Done
    • One Month Later
      portacnb1 earned a badge
      One Month Later
    • Week One Done
      portacnb1 earned a badge
      Week One Done
    • First Post
      m10d earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      270
    2. 2
      snowy owl
      158
    3. 3
      +FloatingFatMan
      145
    4. 4
      ATLien_0
      141
    5. 5
      Xenon
      131
  • Tell a friend

    Love Neowin? Tell a friend!