SpiderBasic

Hi Karu, At the server end, you need to send an allow origin header. for example, in PHP, you need to include this with your response: header('Access-Control-Allow-Origin: *'); The * means any origin, ie any client anywhere - you can filter it to specific IP addresses if these are known and fixed. F...

Update: The SB PUT, PATCH and DELETE do not appear to be sent correctly - they are not appearing in PHP's $_SERVER['QUERY_STRING'] super global. However, when I call the API using my API test tool using PUT, PATCH or DELETE, the APi is picking up the value correctly. Here is an example of a request ...

SpiderBasic 2.20 is reporting success = #False on API calls. However, my API logs say that SB correctly hit the API endpoints with the correct data and that they were processed correctly and the correct response sent back to the Sb generated webpage. When I use my Http test tools to call the APIs di...

@fred, I realise that this was not in the original wishlist post, but if it's not complicated to do, would you mind adding the following HTTP methods for completeness: HEAD OPTIONS TRACE And I wondered whether you were working on adding the ability to access response headers , as we have the ability...

Local SQLite & HTTP verbs.... THANK YOU!

Update: I'll test this over the weekend.

PS - should this not be in the Announcements section rather than Topics?

@Fred - thanks for the clarification. Again, your generosity is much appreciated

Useful, thanks.

By the way, does your offer of free lifetime updates for early adopters still stand?

Thanks for trying Fred. I did suspect that it would be tricky to implement. I appreciate you taking a look.

OK for now I'll just keep using manual JSON construction.

Thank you Fred!

Not yet, no. It's been requested several times, (along with PATCH).

I'm in the same boat as you. I have an API begging for an admin UI, but can't use SpiderBasic to write it as its RESTful.