Where are the arguments in the URL when I make a request?
up vote
0
down vote
favorite
Trying to understand how an HTTP request sends the arguments and their values when I do an HTTP request. For example, if I buy a plane ticket on expedia.com I have to fill in passenger names and credit card details on the browser.
After I press the Book button, I see the URL becomes:
https://www.expedia.com.my/FlightCheckout?tripid=53babb4a-6f91-43cc-a864-6fa5425b74ef&c=78f285ce-0cbf-4914-8fc4-a7bd48312ba3
Naively, I would expect something like this instead:
`https://www.expedia.com.my/FlightCheckout?names=John,Marry&surnames=Smith,Back&credit_card_no=4213877918771999`
Is Expedia is making a request to an API? How are the data being send then?
api http url request
add a comment |
up vote
0
down vote
favorite
Trying to understand how an HTTP request sends the arguments and their values when I do an HTTP request. For example, if I buy a plane ticket on expedia.com I have to fill in passenger names and credit card details on the browser.
After I press the Book button, I see the URL becomes:
https://www.expedia.com.my/FlightCheckout?tripid=53babb4a-6f91-43cc-a864-6fa5425b74ef&c=78f285ce-0cbf-4914-8fc4-a7bd48312ba3
Naively, I would expect something like this instead:
`https://www.expedia.com.my/FlightCheckout?names=John,Marry&surnames=Smith,Back&credit_card_no=4213877918771999`
Is Expedia is making a request to an API? How are the data being send then?
api http url request
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Trying to understand how an HTTP request sends the arguments and their values when I do an HTTP request. For example, if I buy a plane ticket on expedia.com I have to fill in passenger names and credit card details on the browser.
After I press the Book button, I see the URL becomes:
https://www.expedia.com.my/FlightCheckout?tripid=53babb4a-6f91-43cc-a864-6fa5425b74ef&c=78f285ce-0cbf-4914-8fc4-a7bd48312ba3
Naively, I would expect something like this instead:
`https://www.expedia.com.my/FlightCheckout?names=John,Marry&surnames=Smith,Back&credit_card_no=4213877918771999`
Is Expedia is making a request to an API? How are the data being send then?
api http url request
Trying to understand how an HTTP request sends the arguments and their values when I do an HTTP request. For example, if I buy a plane ticket on expedia.com I have to fill in passenger names and credit card details on the browser.
After I press the Book button, I see the URL becomes:
https://www.expedia.com.my/FlightCheckout?tripid=53babb4a-6f91-43cc-a864-6fa5425b74ef&c=78f285ce-0cbf-4914-8fc4-a7bd48312ba3
Naively, I would expect something like this instead:
`https://www.expedia.com.my/FlightCheckout?names=John,Marry&surnames=Smith,Back&credit_card_no=4213877918771999`
Is Expedia is making a request to an API? How are the data being send then?
api http url request
api http url request
asked Nov 19 at 17:12
multigoodverse
1,88753368
1,88753368
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
For sensetive information, usually a POST
request is used. If you want to understand what's going on, simply use the site (press F12 to open the developer tools, go to the Network tab, ensure that the logs are preserved) [this highly depends on the Browser you're using] and you'll see several requests while using the site. What Expedia obviously does is to store your information into a tripid
which seems to be the primary key for the session / booking or whatever. So yeah, even a GET request can be considered to be an API call to FlightCheckout
.
add a comment |
up vote
0
down vote
Some information like filters can be transmitted via URL since they are not sensible information. But you don't want sensible data like transactions, addresses and names to be visible in the URL for security reasons. That's why they are transmitted via POST Requests, you may want to take a look at the HTTP Wikipedia Page for a first introduction into this topic. There should be many learning resources for HTTP Requests and Request Types around the web.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
For sensetive information, usually a POST
request is used. If you want to understand what's going on, simply use the site (press F12 to open the developer tools, go to the Network tab, ensure that the logs are preserved) [this highly depends on the Browser you're using] and you'll see several requests while using the site. What Expedia obviously does is to store your information into a tripid
which seems to be the primary key for the session / booking or whatever. So yeah, even a GET request can be considered to be an API call to FlightCheckout
.
add a comment |
up vote
0
down vote
For sensetive information, usually a POST
request is used. If you want to understand what's going on, simply use the site (press F12 to open the developer tools, go to the Network tab, ensure that the logs are preserved) [this highly depends on the Browser you're using] and you'll see several requests while using the site. What Expedia obviously does is to store your information into a tripid
which seems to be the primary key for the session / booking or whatever. So yeah, even a GET request can be considered to be an API call to FlightCheckout
.
add a comment |
up vote
0
down vote
up vote
0
down vote
For sensetive information, usually a POST
request is used. If you want to understand what's going on, simply use the site (press F12 to open the developer tools, go to the Network tab, ensure that the logs are preserved) [this highly depends on the Browser you're using] and you'll see several requests while using the site. What Expedia obviously does is to store your information into a tripid
which seems to be the primary key for the session / booking or whatever. So yeah, even a GET request can be considered to be an API call to FlightCheckout
.
For sensetive information, usually a POST
request is used. If you want to understand what's going on, simply use the site (press F12 to open the developer tools, go to the Network tab, ensure that the logs are preserved) [this highly depends on the Browser you're using] and you'll see several requests while using the site. What Expedia obviously does is to store your information into a tripid
which seems to be the primary key for the session / booking or whatever. So yeah, even a GET request can be considered to be an API call to FlightCheckout
.
answered Nov 19 at 17:19
maio290
1,364314
1,364314
add a comment |
add a comment |
up vote
0
down vote
Some information like filters can be transmitted via URL since they are not sensible information. But you don't want sensible data like transactions, addresses and names to be visible in the URL for security reasons. That's why they are transmitted via POST Requests, you may want to take a look at the HTTP Wikipedia Page for a first introduction into this topic. There should be many learning resources for HTTP Requests and Request Types around the web.
add a comment |
up vote
0
down vote
Some information like filters can be transmitted via URL since they are not sensible information. But you don't want sensible data like transactions, addresses and names to be visible in the URL for security reasons. That's why they are transmitted via POST Requests, you may want to take a look at the HTTP Wikipedia Page for a first introduction into this topic. There should be many learning resources for HTTP Requests and Request Types around the web.
add a comment |
up vote
0
down vote
up vote
0
down vote
Some information like filters can be transmitted via URL since they are not sensible information. But you don't want sensible data like transactions, addresses and names to be visible in the URL for security reasons. That's why they are transmitted via POST Requests, you may want to take a look at the HTTP Wikipedia Page for a first introduction into this topic. There should be many learning resources for HTTP Requests and Request Types around the web.
Some information like filters can be transmitted via URL since they are not sensible information. But you don't want sensible data like transactions, addresses and names to be visible in the URL for security reasons. That's why they are transmitted via POST Requests, you may want to take a look at the HTTP Wikipedia Page for a first introduction into this topic. There should be many learning resources for HTTP Requests and Request Types around the web.
answered Nov 19 at 17:20
StvnKwlzk
245
245
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53379613%2fwhere-are-the-arguments-in-the-url-when-i-make-a-request%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown