Keygen/Serial generation 403 error

[codecentrix]

Hello everybody,



I am sitting with a peculiar problem.



When E-junkie does the POST with all of the form data to my keygen url there is no "content-type" set in the header

for the request.



This in turn fires some obscure security rule on the hosting solution that I currently use and the request returns

a 403 error immediately without even reaching my asp, php or mvc controller.



Is there a way to add this header in the final POST to the end url ex. "application/x-www-form-urlencoded" ?



Best regards and thank you a great service.

[E-junkie_Guru]

Thanks for reporting your problem; I've referred this to Development for consideration.

[E-junkie_Guru]

Development confirms we always have included a "Content-type: application/x-www-form-urlencoded" HTTP header when we POST to Integration and Keygen URLs. The letter casing there was slightly different vs. typical practice ('Content-type' vs. 'Content-Type'), which shouldn't matter since the RFC specifies that field names are case-insensitive. Even so, we went ahead and updated that anyway to match the more typical casing, just in case your host's security filter was incorrectly rejecting the submissions for that reason.