A simple GET with Grails - http

I have built a simple Grails app, with a domain-class and its controller (with the default scaffold functionality).
I want to use this for an Android app.
I had to get my objects in the JSON format, and thanks to stackoverflow it's been easy ;)
Now I have to put data. I should make a POST call to http://localhost:8080/MyApp/person/save with parameters, I suppose. But I can't succeed using RESTClient or other simple utilities/firefox addons that GET/POST data over an HTTP server.
The response web page is an error web page, saying "Property 'name' can't be null" or similar... as if I have no parameters passed. Perhaps I'm not able to make a POST request on a page?! o_O
And how can I enable GET, in Grails, to insert objects?
Thank you.

Funny, I think I am about 2 weeks ahead of you on a similar project. :)
When you do your Post, be sure and include the ?format=json on the end of your URL and grails will automagically parse the params with no extra code in the controller. Isn't grails wonderful?

Related

How do I auto sign in to Laravel via an API coming from .net?

We have a portal built in asp.net and we need one of the sections to be an embedded frame containing a webapp built in Laravel, however the Laravel webapp has a login and we dont want users having to login twice. So how do I set this up? I understand I need to use this method :
https://laravel.com/docs/5.4/authentication#authenticating-users
The request would be coming from .net and I would parse say the JSON response, but how do I setup laravel to consume that API call? I have never done anything like this before and I dont know where to start. Can someone explain or give me a series of steps? Thank you!
if you have the user id as $id, you can use:
Auth::loginUsingId($id);

How to display a web service (SOAP) JSON result in a Drupal View

I'm a Drupal beginner, and I would like to display a web service (SOAP) result (in JSON) in a page.
I would like to display the result in a table (so I think Drupal View would be nice to display it...), but I don't know how to bring the Web Service result to display it into a View.
I am using the module "wsclient" (http://drupal.org/project/wsclient) together with "Rules" to execute a web service method, and I am able to get its result into a message, but that's all I was able to do until now.
I'm new to Drupal. Can someone help me please, to perform this action in the best way?
I am using Drupal 7.
Thank you!
There's a feature request in the wsclient issue queue for views integration: http://drupal.org/node/1215570
EDIT: as pointed out in the comments below, the following does not apply to the original question:
Have you considered using the Services module instead? There is already views integration for it.

Detect browser when site is accessed

Is there anyway to detect browser version in symfony prior to loading any pages and then run a corresponding action? I was thinking of using modernizr, but I was hoping to not have to rewrite all my views.
Basically what I was hoping I could accomplish is that before the framework attempts to match the url to a route it would first check to see if the user has a particular browser version and if not run another controller instead of the the controller defined in the route.
I think what your suggesting is not a "best practice". I'm assuming you want to route a mobile request to a unique Action method in a Controller. You really shouldn't have a separate controller based client device. This is the job of the (V)view in MVC.
Modernizr is a client side solution with css,js but if youre using symfony, i would prefer server side and that requires the title of this question.. "Detecting browser on request".
While you can custom configure your app to detect the device(and its not to hard), there's also an easier option. Try this bundle. https://github.com/suncat2000/MobileDetectBundle . It does everything and allows for you to make both controller modifications or make twig aware of the browser so you can make smaller changes.

Crawler for Deep-Web calling ASP.NET page

Introduction
I'm developing a web-crawler and I need get the return of ASP.NET forms.
I know about the difficult to try that, but my crawler can get the return of PHP forms or languages like that. I'm using HtmlAgilityPack and call with POST parameters. That works fine.
Problem
My problem starts when I need crawler ASP.NET Forms, with a lot of hiddens fields and other the information (like __VIEWSTATE or __EVENTARGUMENT) for ASP.NET Kernel.
Question
How Can I put for my crawler send a POST call and receive the correct return with the data base filters? Somebody have information about that? Somebody tried something like that?
Thank's everybody.
I'm waiting for a good response.

Does IIS throw away the URL fragment on custom error pages?

I'm using the old 404-rewrite method on a certain site that is tied to IIS6 *.
So if I enter
http://example.com/non-existent/path
it calls my error page like so
http://example.com/catch.aspx?404;http://example.com/non-existent/path
Great.
Except if I call the page with a fragment, like
http://example.com/non-existent/path#with-fragment
I get the same result as above. I can't find the fragment anywhere:
Request.Url
Request.Url.OriginalString
Request.UrlReferrer
Request.RawUrl
headers, server variables, etc
This has come up because I want to resolve paths created by AJAX to their server-side versions.
Is there any way for me to retrieve the original path from my handler?
Thanks.
(*) Please don't suggest I change platform. Obviously I would if I could.
No, there isn't.
The portion of URL after # is never passed to the server per HTTP spec. Has nothing to do with platform.
To work with info after # in javascript you should look at Javascript History plugins/functionality. jQuery has history plugin, asp.net ajax and mvc ajax (partial views et al) have that. Mind you, it's not a very easy thing to implement, you have to get into undo/redo mindset.
It probably won't work if you are trying to handle 404's on the server - server doesn't know that there was something after #. Not sure what you want to do though, 404 handling, or "resolve paths created by AJAX"? What exactly is the goal?

Resources