HTTPSecureSocket NOE

General
1

Hey guys,

I’m occasionally seeing the Xojo framework getting a Nil Object Exception inside the ParseHeaders method inside the HTTPSocket. This is not one of my methods, but Xojo’s. I don’t know what is causing it. I’ve never directly seen this myself but I’ve received error reports on it. Anyone else seen this? If it’s a bug I can file a bug report on it but I don’t have an example project of what is causing this…

NilObjectException
RuntimeRaiseException
RaiseNilObjectException
HTTPSocket._ParseHeaders%%o<HTTPSocket>s
HTTPSecureSocket._HandleNewData%%o<HTTPSecureSocket>
HTTPSecureSocket.Event_DataAvailable%%o<HTTPSecureSocket>
REALPluginMain
SSLSocket.Event_DataAvailable%%o<SSLSocket>
HideMouseCursor
HideMouseCursor
FigureShapeAddCubic
enableMenuItems
serialClearBreak
MenuItemConstructor
MenuItemConstructor
MessageDialogShowModal
MessageDialog.ShowModal%o<MessageDialogButton>%o<MessageDialog>
mainWindow.mainWindow.CheckDemoTimer_Action%%o<mainWindow.mainWindow>o<Timer>
TimerEnabledGetter
KillTimer
TranslateMessageEx
enableMenuItems
Application._CallFunctionWithExceptionHandling%%o<Application>p
enableMenuItems
RuntimeRun
REALbasic._RuntimeRun
_Main
wWinMain
__chkstk
BaseThreadInitThunk
RtlUserThreadStart
2

My guess is a malformed or non-HTTP 1.0 compliant response.

The classic HTTPSocket should not really be used anymore as most of the web is using HTTP 1.1 and moving to 2.0.

3

Well, since it’s my web server on the other end, it shouldn’t really matter! :slight_smile: And anyhow, Xojo’s framework should be able to handle such a malformed response w/o throwing an exception.

So I take it then you are recommending we use Xojo.Net.HTTPSocket isntead since it’s 1.1?