Forum Discussion
Lightem
Occasional Contributor
I saw the same on Mailinators' docs as well and I have no idea why it needs to work the way is does.
I did find a horrible, ugly solution to my problem, shown in the screenshot.
I added the HTTP/1.1 to the domain value and the entirety of the messege came across.
The scary part. The final URL
...domain=true%20HTTP%2F1.1 HTTP/1.1
I have no idea why this would even be accepted as a valid request.
richie
6 years agoCommunity Hero
Hey Lightem
Wow! Well, you got it working, but God that's ugly.
I'd still be tempted to raise a service request with them.....cos the api doesn't work as specced out in mailinator's requirements....and they need to know that....although i seriously doubt they don't know about it tbh.
Sorry i couldn't straighten it out for you, but at least you've found a workaround,
Nice one,
richie
Wow! Well, you got it working, but God that's ugly.
I'd still be tempted to raise a service request with them.....cos the api doesn't work as specced out in mailinator's requirements....and they need to know that....although i seriously doubt they don't know about it tbh.
Sorry i couldn't straighten it out for you, but at least you've found a workaround,
Nice one,
richie
Related Content
- 3 years agoAAB
- 5 years agovikassardesai
Recent Discussions
- 4 days agominhng