Under Files & Links define the Default location for new attachments attribute to be any value exept the Same folder as current file . My definition and recomendation:
\n![\"|90%?my](\"https://<metadata.url>.netlify.app/attch/Pasted%20image%2020220424171759.png\" "\\"my")
\nIt's a perfect combination of manage privacy as well as lighting site and publish easily.
change the value of the variable publishAttachementsDir to contain the output directory. for exemple:
const publishAttachementsDir = 'attch';\nfor every attachments directory you have to map it to the _site/<publishAttachementsDir> directory.
\nSo below this line you can add as many mapping as needded for your attachments folders you may like to share from your vault to your site.
\nIt can be done through:
eleventyConfig.addPassthroughCopy({<fromDir>:<toDir>});\nfor example:
\neleventyConfig.addPassthroughCopy({"src/MyObsidian/public/attachments":`${publishAttachementsDir}`});\nIn your note, you can include your image with the format  for example:
\n![\"My](\"https://imgs.developpaper.com/guest/2019/01/logo.png\" "\\"This"){kind=logo}
\nExample from the local files (stayed at src/MyObsidian/public/attachments):
\n![\"My](\"https://<metadata.url>.netlify.app/attch/msedge_0sbOL3eK3s.png\" "\\"hill")
\n![\"http|100px\"](\"https://<metadata.url>.netlify.app/attch/HTTP_logo.svg\"){kind=logo}
In computing, POST is a request method supported by HTTP used by the World Wide Web. By design, the POST request method requests that a web server accept the data enclosed in the body of the request message, most likely for storing it. It is often used when uploading a file or when submitting a completed web form.
\nIn contrast, the HTTP GET request method retrieves information from the server. As part of a GET request, some data can be passed within the URL's query string, specifying (for example) search terms, date ranges, or other information that defines the query.
\nAs part of a POST request, an arbitrary amount of data of any type can be sent to the server in the body of the request message. A header field in the POST request usually indicates the message body's Internet media type.
\nThe world wide Web and HTTP are based on a number of request methods or 'verbs', including POST and GET as well as PUT, DELETE, and several others. Web browsers normally use only GET and POST, but RESTful online apps make use of many of the others. POST's place in the range of HTTP methods is to send a representation of a new data entity to the server so that it will be stored as a new subordinate of the resource identified by the URI. For example, for the URI http://example.com/customers, POST requests might be expected to represent new customers, each including their name, address, contact details and so on. Early website designers strayed away from this original concept in two important ways. First, there is no technical reason for a URI to textually describe the web resource subordinate to which POST data will be stored. In fact, unless some effort is made, the last part of a URI will more likely describe the web application's processing page and its technology, such as http://example.com/applicationform.php. Secondly, given most web browsers' natural limitation to use only GET or POST, designers felt the need to re-purpose POST to do many other data submission and data management tasks, including the alteration of existing records and their deletion.
\nEfforts by some influential writers to remedy the first point began as early as 1998. Web application frameworks such as Ruby on Rails and others make it easier for designers to provide their users with semantic URLs. With regard to the second point, it is possible to use client-side scripting, or to write standalone apps, to make use of the other HTTP methods where they are relevant, but outside of this most web forms that submit or alter server data continue to use POST for the purpose.
\nThat is not to say that every web form should specify method="post" in its opening tag. Many forms are used to specify more precisely the retrieval of information from the server, without any intention of altering the main database. Search forms, for example, are ideally suited to having method="get" specified.
\nThere are times when HTTP GET is less suitable even for data retrieval. An example of this is when a great deal of data would need to be specified in the URL. Browsers and web servers can have limits on the length of the URL that they will handle without truncation or error. Percent-encoding of reserved characters in URLs and query strings can significantly increase their length, and while Apache HTTP Server can handle up to 4,000 characters in a URL, Microsoft Internet Explorer is limited to 2,048 characters in any URL. Equally, HTTP GET should not be used where sensitive information, such as usernames and passwords, have to be submitted along with other data for the request to complete. Even if HTTPS is used, preventing the data from being intercepted in transit, the browser history and the web server's logs will likely contain the full URL in plaintext, which may be exposed if either system is hacked. In these cases, HTTP POST should be used
\n", "date_published": "2022-03-01T00:00:00Z" },{ "id": "https://<metadata.url>.netlify.app/thirdpost/", "url": "https://<metadata.url>.netlify.app/thirdpost/", "title": "ORDS - Source Type Options", "content_html": "Defines the source implementation for the selected HTTP method.
\nOptions include:
\nSELECT 'content_type', column FROM . . .\n\n\nwhere 'content_type' is a string passed to the browser to be used to identify the incoming data, for example 'image/jpeg', and column is the name of the column containing the source of the data being sent back. The Media Resource Source type is typically used for media objects, such as images, where the data will be directly handled by the recipient making the call.
\n
NOTE: The following are considered deprecated as they represent options specific to APEX Based REST Services.
\nRead my other posts:
\nFirst post
\nThird post
Beitar Jerusalem Football Club (Hebrew: 诪讜注讚讜谉 讻讚讜专讙诇 讘讬转"专 讬专讜砖诇讬诐, romanized: Moadon Kaduregel Beitar Yerushalayim), commonly known as Beitar Jerusalem (讘讬转"专 讬专讜砖诇讬诐) or simply as Beitar (讘讬转"专), is an Israeli football club based in the city of Jerusalem, that plays in the Israeli Premier League, the top tier in Israeli football. The club has traditionally worn kit colours of yellow and black. The team has played its home matches in Teddy Stadium. The stadium is the largest stadium in Israel with a capacity of 34,000.
\n![\"Beitar|50%\"](\"https://upload.wikimedia.org/wikipedia/en/6/61/Beitar_Jerusalem.png\")
\nThe club is one of the most popular in Israel and is among the Israeli clubs with the highest number of fans in the country. The club was founded in 1936 by Shmuel Kirschstein and David Horn, who chaired the similarly named Betar branch in Jerusalem. Several team members were also part of the outlawed Irgun and Lehi militias closely associated with the right-wing Revisionist Zionism movement. Beitar's fans have become a highly controversial political symbol in Israeli football culture, unofficially aligned with the Revisionist Zionist movement and to the right-wing Likud party. The club, whose fanbase is notorious for its anti-Arab racism and anti-Muslim religious bigotry, remains the only one in the Israel Premier League to have never signed an Arab player, although the club signed four non-Arab Muslim players in the past.
Beitar held its first games as an professional football team in the "Dajani field", which was located in the old Katamon neighborhood. After the War of Independence and the establishment of the State of Israel, the team's home was officially moved to the YMCA Stadium, which has since become the team's regular home ground, until 1991, when the team moved to Teddy Stadium.
\nTeddy Stadium, Beitar's home ground.
\nIn 1991, Beitar has moved to the Teddy Stadium, named after longtime Jerusalem mayor Teddy Kollek. Initially the stadium was two-sided and held 12,000 spectators. This was increased to 21,600 when a third side was completed in 1997. The fourth side of the stadium was completed in the summer of 2013 in anticipation of the UEFA under 21 championship hosted by Israel, increasing the capacity of the stadium to 34,000 seats.
The ground has been dubbed Gehinom (lit. Hell) by club supporters, for the hostile atmosphere it presents to visiting teams and their fans.
\nAll of the departments of Beitar Jerusalem train in the training complex at Beit Vagan. The complex includes locker rooms for the alumni group and the youth department, gyms, physiotherapy rooms, dining room, cloakrooms and treatment rooms. The complex contains three training fields, two of them with synthetic grass. Each of the fields has two Tribunes on both sides, and all contain a total of about 750 seats.
\nThe club's offices have been in the complex since 2009, and there is a fan shop inside the complex that sells cheerleading and merchandise products for the group's fans.
\n", "date_published": "1998-05-09T00:00:00Z" } ] }