<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rajendra Prasad Padma on Medium]]></title>
        <description><![CDATA[Stories by Rajendra Prasad Padma on Medium]]></description>
        <link>https://medium.com/@rajendraprasadpadma?source=rss-62d540629b27------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*dji4MVm5C3L51LdPiRj6Sg.png</url>
            <title>Stories by Rajendra Prasad Padma on Medium</title>
            <link>https://medium.com/@rajendraprasadpadma?source=rss-62d540629b27------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:43:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rajendraprasadpadma/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[“What the CORS” ft Spring Boot & Spring Security]]></title>
            <link>https://rajendraprasadpadma.medium.com/what-the-cors-ft-spring-boot-spring-security-562f24d705c9?source=rss-62d540629b27------2</link>
            <guid isPermaLink="false">https://medium.com/p/562f24d705c9</guid>
            <category><![CDATA[spring-security]]></category>
            <category><![CDATA[spring-boot]]></category>
            <category><![CDATA[rest-api]]></category>
            <category><![CDATA[cross-origin]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Rajendra Prasad Padma]]></dc:creator>
            <pubDate>Sat, 13 Mar 2021 16:55:49 GMT</pubDate>
            <atom:updated>2021-03-13T16:55:49.505Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*swMqP14hgSpEmK7GG-WV3g.jpeg" /><figcaption>Title</figcaption></figure><p>Ok. One fine day, I was trying to build a simple Rest API that exposed endpoints to create,read,update,delete a single resource on my server. I wanted to use React to make a small form that will submit these requests.</p><p>Beware, the following React form is so advanced. You have to be atleast a Ninja level React developer to come up with this kind of form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w4ApbqUZNYynOR4G5kDveA.png" /></figure><p>Dont be jealous guys.!</p><p>So my Rest Api (made with spring boot) was running on ‘<em>http://localhost:8080</em>’ &amp; my React App was running on ‘<em>http://localhost:3000</em>’</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/889/1*Y6hb8Z6DHaPJdLN9r8GweA.jpeg" /><figcaption>Wife Overthinking meme</figcaption></figure><p>Code was all ready and prepped to make that first ever post request to create the resource on server. I was waiting eagerly as the folks at JPL during perseverance touch down.</p><p>Then I saw this on my console</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ps05-j8MbO4Btga4WumzSw.png" /><figcaption>What the CORS!!!</figcaption></figure><p>And when I went to my network tab in ‘developer console’ to dig further. I saw these two requests lying around</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FKH3Eh2d_ljSP5GPromWyw.png" /><figcaption>Developer Tools — Network Tab</figcaption></figure><p>I was using the fetch api to make the below POST request from my react code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gbTabhilGErda6xzy8XJCQ.png" /><figcaption>React Code</figcaption></figure><p>After hitting that submit button from my page, i was confused of two things:</p><ol><li>Why did my POST fail</li><li>Why are there two requests in network tab of my server as shown in the developer console screenshot</li></ol><p><strong>Introducing CORS</strong></p><p><a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS">CORS</a> is a way for browsers to understand if a particular javascript code running on it(Ex: My React Code — http://localhost:3000)is allowed to request a resource from the server(My Spring Boot Rest Api running on the server — <a href="http://localhost:8000)">http://localhost:8000)</a> . If they are not allowed by servers, then browsers simply throw a CORS exception.</p><p>Lets try to understand this with error message i received in the console:</p><p><em>Access to fetch at ‘</em><a href="http://localhost:8080/airports&#39;"><em>http://localhost:8080/airports&#39;</em></a><em> from origin ‘</em><a href="http://localhost:3000&#39;"><em>http://localhost:3000&#39;</em></a><em> has been blocked by CORS policy: Response to preflight request doesn’t pass access control check: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled.</em></p><p>Here the key word to understand is ‘origin’. ‘origin’ is the combination of ‘protocol://host:port’. So the request is being made from an origin called ‘http://localhost:3000’ and the request is sent to origin ‘http://localhost:8080’. So these are two different origins trying to communicate. So in these cases , the browsers verify if the requestor (http://localhost:3000) is allowed to request a resource from requestee (http://localhost:8080). If requestor is not allowed to , then we see this nasty CORS error while making requests.</p><p>But why do we see two requests happening in network tab?</p><p>If you notice carefully , one request is having the Type = preflight and another one (i.e., the actual fetch making POST) request has type = ‘CORS error’ from screenshot above. So Browsers don’t immediately send the POST request first, they try to check which “origin” is whitelisted/allowed by server first. In order to do this check, they send out an OPTIONS request to the server. This is often referred to <em>“preflight” </em>request.</p><p>So what is the browser actually expecting from this preflight request?</p><p>Browser is expecting to receive a response header back from the server which tells it that “am cool with having this request”.</p><p>And which response header is that exactly?</p><p>“<a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin"><em>access-control-allow-origin</em></a>” — This is the header where the whitelisted origins are mentioned. If localhost:3000 is present on the whitelisted header then we are open for business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/520/1*5jtpB04ZO_MVnj7au8Hvdw.jpeg" /><figcaption>Bouncer Meme</figcaption></figure><p>Lets see what is in the failed preflight request.</p><p>The Request Method is ‘OPTIONS’ and its forbidden (403) to make that request on the server. And my Response headers don’t have anything mentioned as ‘Access-Control-Allow-Origin’. So Basically, The preflight request itself failed because “OPTIONS” request method was not defined on the server side.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lVdstP4uoZeVh-uuE-rcOQ.png" /><figcaption>Developer Tools — Headers</figcaption></figure><p>All I have at my controller are these basic CRUD request mappings (GET,POST,PUT,DELETE)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_AIkRvBcFnlPFqZSM8v-lA.png" /><figcaption>Rest Controller Code</figcaption></figure><p>So now the original question? How do i allow preflight to check which origin is allowed and how do i whitelist “http://localhost:3000” as a qualified origin.</p><p>Spring Boot offers a simple solution through its annotation @CrossOrigin. Simply put it on top of your controller class like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r_Rns8YDo0HLWte9Njg4FA.png" /><figcaption>Rest Controller Code</figcaption></figure><p>Now I restarted my spring boot application and retried posting the resource.</p><p>And it worked</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yH5I4MsjYXIE9__bNjZ1gg.png" /><figcaption>Full Screenshot Of Form And Developer Tools</figcaption></figure><p>You will see now that both preflight and the post request made it out with ‘200 — A Ok ;)’</p><p>Lets examine the preflight request and response headers now.</p><p>In the request headers of preflight, the request method is ‘OPTIONS’ and in response headers, you will notice that</p><p>‘Access-Control-Allow-Origin’ : * (This indicates that any origin can make a request to resource on the server, so my react application also qualifies to send the request)</p><p>‘Access-Control-Allow-Methods’ : POST (preflight confirmed that POST that is about to be made is qualified)</p><p>‘Allow’ : GET,HEAD,POST,PUT,DELETE,OPTIONS,PATCH.</p><p>Before making the @CrossOrigins change on the server, preflight request got 403 status since OPTIONS was not allowed on the server. But now you can see that all the request methods are being allowed by the server. So preflight which is “OPTIONS” request goes through fine even if it doesn’t have any endpoint declared on the server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Hh_rE6SMJIHo_1AOt7F4g.png" /><figcaption>Developer Tools — Headers</figcaption></figure><p>Just declaring @CrossOrigins on the controller opens the gates for all the origins and methods to come and hit your server. But in a serious application, we wouldn’t want that. So you can customize the origins and methods that you want to filter at server by using these attributes in @CrossOrigins</p><ol><li>origins = “http://localhost:3000”</li></ol><p>(This will only allow my react app to request)</p><p>2. methods={RequestMethod.<em>GET</em>,RequestMethod.<em>POST</em>,RequestMethod.<em>PUT</em>,RequestMethod.<em>DELETE</em>}</p><p>(You can define what methods are allowed from requests)</p><p>There are others to declare what headers are allows, and if credentials are allowed or not etc.., You can explore them on your own</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iTJD5kE9dt3LKjMFOLjiCQ.png" /><figcaption>Rest Controller</figcaption></figure><p><strong>Phase II — Attach Basic Authentication to my requests using spring security</strong></p><p>Ok. After this confidence boost, i wanted to try attaching spring security to my rest api. Wanted to allow basic authentication as a way to authenticate the requests</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*7iESabtF4JyGt3OKjP4mFQ.jpeg" /><figcaption>Drake meme</figcaption></figure><p>Being a Ninja that i am , Went and added Spring security starter dependencies to my pom.xml and udpated maven dependencies and started up my server. Once server restarts, spring security puts in a layer of authentication to the application with default username as ‘user’ and password is some hash that spring security generates randomly everytime.</p><p>Now, I made the same post request from react application.</p><p>And once again, the dreaded CORS exception was back</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ogddaGiQosEQQORiWCcs_Q.png" /><figcaption>Full Screenshot of Page and Console</figcaption></figure><p>Went into network to debug further.</p><p>There was only one post request and no preflight request.The response to the post request doesn’t have the ‘Access-Control-Allow-Origin’ set. Also we see new <strong>WWW-Authenticate:</strong>Basic realm=”Realm” header.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oU0cq0wPwc58eAhbPGsE0A.png" /><figcaption>Response Headers</figcaption></figure><p>So basically after enabling the spring security, we are expected to do two things:</p><ol><li>Send the basic authentication request from our client while making request</li><li>Make our server send the Access-Control-Allow-Origin Flag indicating that the react application is qualified origin.</li></ol><p>But wait, we already mentioned @CrossOrigins at our controller didn’t we?</p><p>Yeah, But they aren’t being considered when spring security is enabled, we need a way through this.</p><p>Lets, attack this one step at a time.</p><ol><li><em>Send the basic authentication request from our client while making request</em></li></ol><p>Since am using fetch, in the parameters i send while making the POST call from React, I need to attach the below header information:</p><p>“Authorization”:”Basic <em>Base64encoded(username:password)</em>”</p><p>lets say my user name is — user</p><p>password is — harambe</p><p>I can use a function in react called btoa and pass username and password to it like — btoa(user:harambe). The btoa method returns the base64 encoded string. So this looks something like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F-QDcG2XELwNfxBVKpavlQ.png" /><figcaption>React with authorization</figcaption></figure><p>Don’t forget to keep &lt;space&gt; between Basic and btoa(username:password) method. This helps with authentication.</p><p>Now lets try that post call again</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ig2Bk3U7htbREoG0G0DCVQ.png" /><figcaption>What the cors!! part 2</figcaption></figure><p>Well, well , well — who we have here. Went to network to see both preflight and post request</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f_DuCSopNs-1DCmbsVHOHw.png" /><figcaption>Preflight + POST</figcaption></figure><p>The pattern feels the same like what we have encountered before adding spring security to the project. One preflight(OPTIONS) request that is unauthorized and another CORS exception in fetch POST call(the actual call).</p><p>Digging into the preflight request and response , i see that <strong><em>no allow-access-control-origin returned by server and it was expecting authentication even on the OPTIONS request</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tFqmE2NtiS4YYhXyGdu5aw.png" /><figcaption>Developer Tools — Headers</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/507/1*EgiQUZ1SzblRFdonv9gH1g.jpeg" /><figcaption>Contemplating pablo meme</figcaption></figure><p>After spending a good half of my weekend into looking for a way to configure spring security to allow cross origin request, i stumbled upon this piece of code</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RaSHqssQN42nvhFbbrOIHQ.png" /><figcaption>Web Security Config</figcaption></figure><p>Configure the spring security config by calling these methods that come out of the box in your main Spring Application that hosts this Rest API.</p><p>here the method</p><ol><li>cors() -&gt; tells spring security to enable cors. So Now server is ready to whitelist/filter the origins. So be mindful that we are still going to set the origins list</li><li>httpBasic() -&gt; tells spring security that clients are going to authenticate the requests through basic authentication method. So spring security is tuned to read the ‘Authorization’:’Basic #hash’ that we are sending from client. If its a valid authentication details, spring security will let us through</li></ol><p><em>For the rest of the methods you see on the code, i will plan another blog post.</em></p><p>Now, cors() is just enabled, but we still have to configure which origins are whitelisted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M6BPiBLewjZ5efZxZftpBQ.png" /><figcaption>Rest Controller</figcaption></figure><p>So, here you see in the controller, I have added my</p><ol><li>origins = “http://localhost:3000” .which is my react code</li><li>allowCredentials = true. This is important if you are using any form of authentication</li></ol><p>By default, the @CrossOrigin allows all the request methods and headers. So <br>preflight request wouldn’t be having a problem now.</p><p>Now, let us hit that post button again</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*snD-klvj5MkgNAFDA2-cpw.jpeg" /><figcaption>Button stress meme</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_U2_93YJSOXoEvQEvpI6eA.png" /><figcaption>Final Glory</figcaption></figure><p>Finally, The sweetness of Glory.</p><p><em>Please ignore the second request here , its not from preflight. I wrote a logic to do ‘Get’ after posting something to list the items as u see in screenshot.</em></p><p>Lets check the POST request and response headers affected with our configuration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tr-ojF4W9g9i3nWW4QyXdw.png" /><figcaption>Developer Tools — Response Headers</figcaption></figure><p>You can see that ‘Access-Control-Allow-Credentials’ flag is set to true &amp; also allow-origin shows the react application origin.</p><p>Hope this makes your day !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=562f24d705c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[spring Boot Microservice deployed to docker container]]></title>
            <link>https://rajendraprasadpadma.medium.com/spring-boot-microservice-deployed-to-docker-container-64bbecb399f4?source=rss-62d540629b27------2</link>
            <guid isPermaLink="false">https://medium.com/p/64bbecb399f4</guid>
            <dc:creator><![CDATA[Rajendra Prasad Padma]]></dc:creator>
            <pubDate>Sat, 11 Apr 2020 19:05:01 GMT</pubDate>
            <atom:updated>2020-04-11T19:08:48.534Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/355/1*AXJy5_RAmpAQuTgdMvQ6WQ.jpeg" /></figure><p><strong>Spring Boot Microservice deployed to docker container</strong></p><blockquote>I have always fantasized about writing a post about creating a basic microservices app using spring boot and deploy them into docker container. Yeah I know there are tons of blogs + videos which show exactly that, but its a fantasy</blockquote><p>Let’s begin !</p><p>Ingredients:</p><p>2 spring boot microservices</p><p>1 eureka server</p><p>1 gateway server</p><p>Docker</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64bbecb399f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Object references an unsaved transient instance — save the transient instance before flushing]]></title>
            <link>https://rajendraprasadpadma.medium.com/object-references-an-unsaved-transient-instance-save-the-transient-instance-before-flushing-1bede249108?source=rss-62d540629b27------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bede249108</guid>
            <category><![CDATA[error]]></category>
            <category><![CDATA[flush]]></category>
            <category><![CDATA[hibernate]]></category>
            <category><![CDATA[jpa]]></category>
            <category><![CDATA[transient]]></category>
            <dc:creator><![CDATA[Rajendra Prasad Padma]]></dc:creator>
            <pubDate>Wed, 27 Nov 2019 03:39:49 GMT</pubDate>
            <atom:updated>2019-11-27T03:39:49.627Z</atom:updated>
            <content:encoded><![CDATA[<h3>Object references an unsaved transient instance — save the transient instance before flushing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qTFEIyTec3OseBhjG1IFWw.png" /></figure><p>Yep, We have all been there. Remember that familiar looking stacktrace above?</p><p>Here is the code that produce this error:</p><figure><img alt="Code throwing error" src="https://cdn-images-1.medium.com/max/713/1*-7T5Q-IOMsggIw6u8TMg9Q.png" /></figure><p>Star and Rating are two entities where Star has OneToOne mapping to Rating</p><figure><img alt="Star" src="https://cdn-images-1.medium.com/max/731/1*46rhre_QiNVLTayliJkw2Q.png" /></figure><figure><img alt="Rating" src="https://cdn-images-1.medium.com/max/809/1*SBJLaKkvhMlDzWwD7rgH-g.png" /></figure><p>In the code, we notice that we have created the child i.e., Rating but did not persist it to the database yet( we didn’t call save onto the rating object). But we are trying to set the rating object inside the setter of the Star object and we are trying to save the star entity.</p><p>How could we possibly map the star to the rating, if there is no rating record in the DB yet?</p><p>That is where we see the below error -&gt;</p><p>Object<strong><em>(Star)</em></strong> references an unsaved transient instance<strong><em>(Rating)</em></strong> — save the transient instance<strong><em>(Rating)</em></strong> before flushing<strong><em>(Saving Star)</em></strong></p><p>Well, how would we resolve this?</p><p>Simple. Just tell to hibernate to save the Rating before saving the star i.e., tell the parent to save the child before forming an association.</p><p>This can be done by using cascade attribute on OneToOne mapping:</p><figure><img alt="Using Cascade" src="https://cdn-images-1.medium.com/max/767/1*pcE36fjJcJPdBosmFpaoOw.png" /></figure><p>Cascade tells hibernate that whatever operations are being performed on the parent are propagated to objects in relationship. In the above case the parent is star and create action is propagated to child i.e., Rating.</p><p>Hope this helps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bede249108" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Will your schema.sql file execute when spring.jpa.hibernate.ddl-auto is set to create-drop?]]></title>
            <link>https://rajendraprasadpadma.medium.com/will-your-schema-sql-file-execute-when-spring-jpa-hibernate-ddl-auto-is-set-to-create-drop-dbece3b5ecce?source=rss-62d540629b27------2</link>
            <guid isPermaLink="false">https://medium.com/p/dbece3b5ecce</guid>
            <category><![CDATA[hibernate]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[spring-boot]]></category>
            <dc:creator><![CDATA[Rajendra Prasad Padma]]></dc:creator>
            <pubDate>Mon, 18 Nov 2019 19:03:05 GMT</pubDate>
            <atom:updated>2019-11-18T19:03:05.281Z</atom:updated>
            <content:encoded><![CDATA[<p>Nope. The schema.sql file, which is a good old fashioned database-ddl-script that we put in our spring-boot application doesn’t get executed if you put the spring.jpa.hibernate.ddl-auto to ‘create-drop’. By setting ‘create-drop’ value , we are essentially asking hibernate to read the definition of our table from entity class/xml configuration and create it. So, it ignores schema.sql even if it is in the classpath. If you want your schema.sql to be picked up, try setting the spring.jpa.hibernate.ddl-auto to none.</p><p><a href="https://stackoverflow.com/questions/58893865/why-isnt-hibernate-picking-up-database-sequence-for-primary-key-column-while-in">https://stackoverflow.com/questions/58893865/why-isnt-hibernate-picking-up-database-sequence-for-primary-key-column-while-in</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dbece3b5ecce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Difference between spring data jpa and hibernate?]]></title>
            <link>https://rajendraprasadpadma.medium.com/difference-between-spring-data-jpa-and-hibernate-8aa247d22c6d?source=rss-62d540629b27------2</link>
            <guid isPermaLink="false">https://medium.com/p/8aa247d22c6d</guid>
            <category><![CDATA[spring-boot]]></category>
            <category><![CDATA[jpa]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[hibernate]]></category>
            <category><![CDATA[spring-data-jpa]]></category>
            <dc:creator><![CDATA[Rajendra Prasad Padma]]></dc:creator>
            <pubDate>Sat, 16 Nov 2019 16:55:20 GMT</pubDate>
            <atom:updated>2019-11-16T16:58:03.106Z</atom:updated>
            <content:encoded><![CDATA[<p>Well, Hibernate is a provider of JPA i.e, a Vendor that provides the implementation of java persistence api. There are many other java persistence api providers like TopLink and EclipseLink in the market but hibernate is quite wellknown amongst the community.</p><p>Spring Data Jpa on the other hand is a library that adds additional wrapper code on top of the provider (i.e., hibernate,TopLink,EclipseLink etc..,) to cut through the additional boiler plate code that is required in order to interact (CRUD) with the persistent stores(Databases).</p><p>By default hibernate will be used as the default provider for the jpa. (I told you, hibernate is quite cool in the community )</p><figure><img alt="spring boot starter dependency for spring-boot-starter-data-jpa" src="https://cdn-images-1.medium.com/max/1024/1*cxxLaYkJJZHuiTbThPyiXA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8aa247d22c6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>