HTMLViewer error 204 ( in 64 bits mode )

Targets macOS
#1

Hi, does somebody know why HTMLViewer is not working in my example?
When compiling for 32 bits it does as wanted but in 64 bits mode I get error 204 and I don’t know how to resolve this.
Using macOS 10.14.6 and Xojo 2019r1.1

http://xinfinite.nl/download/xojo/bug/htmlviewer.xojo_binary_project.zip

#2

According to the docs, this is a success code. Winky says:

[quote]204 No Content
The server successfully processed the request and is not returning any content.[/quote]

The docs say that the codes from error event are standard HTTP response codes, perhaps you should be handling those instead of treating as error.

#3

isn’t is the fact that you need to connect with https:// nowaday instead of http:// on most web sites ?
also don’t forget the app security flags :
http://documentation.xojo.com/topics/communication/internet/using_non-secure_urls_on_macos_and_ios.html
https://documentation.xojo.com/topics/application_structure/mobile/using_a_plist.html

#4

[quote=452604:@Jean-Yves Pochez]isn’t is the fact that you need to connect with https:// nowaday instead of http:// on most web sites ?
also don’t forget the app security flags :
http://documentation.xojo.com/topics/communication/internet/using_non-secure_urls_on_macos_and_ios.html
https://documentation.xojo.com/topics/application_structure/mobile/using_a_plist.html[/quote]
I use https so thats not the issue!

#5

[quote=452601:@Tim Streater]According to the docs, this is a success code. Winky says:

The docs say that the codes from error event are standard HTTP response codes, perhaps you should be handling those instead of treating as error.[/quote]
Well, the same code build for 32bits architecture is working very well!

#6

Quite possibly it uses a legacy api on macOS that doesnt impose this requirement

#7

So maybe Safari is also using the legacy api? The URL is working within all browsers. Isn’t it possible that Xojo is something doing strange?

#8

Safari could be doing almost anything

#9

@Jaap Cammeraat - make sure you are setting a valid user-agent string. The server could simply be refusing to send content if that’s blank.

#10