Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
Can someone help me in getting more information about
BasicHttpEntityEnclosingRequest(String method, String uri).
This did not help me understand the said topic.
What are you trying to do with BasicHttpEntityEnclosingRequest? An entity in httpcomponents refers to the body or the payload of the request.
You should be using sub classes of HttpEntityEnclosingRequestBase that is HttpPut, HttpPost or HttpPatch when sending a HTTP request that has a body.
http://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/client/methods/HttpEntityEnclosingRequestBase.html
You should read the HttpClient Tutorial, particularly chapter 1 to get you started.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 1 year ago.
Improve this question
I am trying to get values from database in an anchor tag, but it's not working. My code is :
<a href="{{url('admin/$getStudyLevel->slug_name/$getStudyLevel->id')}}" class="small-box-
footer">Get In <i class="fas fa-arrow-circle-right"></i></a>
Thanks
There are few way to pass param to url .Suppose consider you have following route
Route::any("user/{id}/{email}",[UserController::class,'index'])->name("userDetail");
then in your view using route name you can pass
User Detail
if you are using url then
User Detail
or
User Detail
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I was wondering of what could be the advantages or disadvantages of using slug instead of id when looking for a model or for urls.
Because there is a possibility to bind directly the url so that in the web.php file, this url /users/{user} will become the following:
with id:
domain.com/users/1
or with slug:
domain.com/users/IQii33XAQhldEK
Thanks
IQii33XAQhldEK is not a slug, a slug would be domain.com/users/patrissol-kenfack.
In the case of the slug, the 2 benefits are:
Better readability for humans,
Better for SEO, because Google will see the keywords in the URL.
If you use id in the url, it could mean that users would be able to know what the id of the resource they are viewing are. Usually, this won't be much of an issue, but if proper security practices are not followed, users could modify resources using this id by passing it implicitly (So make sure to use $fillable or $guarded) . For example, a malicious user could simply put a
<input type="text" name="id" value="<the-id-of-any-other-resource>"
And if you insert or update models with $request->all(), it could end up modifying the id of that resource.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 4 years ago.
Improve this question
I have two controllers:
AdminController
ProductController
AdminController has some functions:
index
create
etc
ProductController also has some functions:
index
create
etc
In admin dashboard there is a button Product. When I will click it it will call ProductController index page.
Then in Product button subsection create, edit, delete etc will be available.
at last my url will be: admin/product/create
How is this possible? Give me idea.
Have a look at Routing Prefixes. This way, the admin slug is always there but you can bind the rest of the actions from there. Furthermore, you can have multiple prefixes within each other if you'd like. If you are not familiar with the routes.php, I'd suggest reading through the documentation and just simply play with it a bit.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am making a website using laravel. I have a search page where users can search for products and a SearchController which does the actual searching.
Right now, I am passing the form data to the controller with a post method (search string, filters, etc.), it works brilliantly!
However, I see that almost every website passes the search parameters in the URI using a query string. Why is tht better? Should I be doing the same?
Thanks!
It's good to keep query parameters in uri for SEO purpose. If you use post method, when you refresh page you won't get data. If you use get method, even page is refreshed you will get data. If you pass query in uri, you can directly get the data by accessing that url.
The search parameter in URL is helpful when the user wants to search more item related to that without refreshing the page. You can do it by ajax and php.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
A very simple scenario, I have a page with a form, I want to submit it to the server and if data is successfully validated display different stuff/data/page (I don't care if the URL changes or stays the same). What is the best way to do it?
Some more data - I need a wizard type UI and it needs to work with JavaScript disabled.
You want to check the ModelState.isvalid property. If all the data passes validation, it will return true, otherwise false.
In your controller
[HttpPost]
public ActionResult SomeAction (SomeModel viewModel)
{
if (ModelState.IsValid)
{
//display different stuff/data/page
}
else
{
return View(viewModel);
}
}