Detect also NegTokenArg packet.
in same way as NegTokenInit has, which caused that packet was passed to application instead of being processed by Waffle.
Add troubleshooting story on HTTP 1.0 protocol with .Net client
Full discussion on group https://groups.google.com/d/msg/waffle-users/Nisu-m19_nI/HLgaNhfBEw4J
Maven central link instead of Sonatypes
…a function was too small.
After some wonderful help, I'm updating the setup with what I've learned and how we fixed my multiple build issues I'm not familiar with the ML this page uses, so I've stuck the major points as bullets. I wanted to place them as subsections, but this works too. It's pretty extensive but it works. I hope it'll help people get this working too.