<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://www.taxtmi.com/rss_sitemap/rss_feed_blog.xsl?v=1750492856"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>2022 (8) TMI 1622 - DELHI HIGH COURT</title>
    <link>https://www.taxtmi.com/caselaws?id=468438</link>
    <description>Writ jurisdiction under Article 226 depends on the respondent authority being located within the court&#039;s territorial limits or on some part of the cause of action arising there. On the stated facts, the disciplinary proceedings, enquiry, and impugned order all originated in Jharkhand, and the respondent had no office in Delhi. The petitioner&#039;s residence in Delhi was insufficient to confer jurisdiction. The Delhi High Court therefore lacked territorial jurisdiction to entertain the writ petition.</description>
    <language>en-us</language>
    <pubDate>Tue, 30 Aug 2022 00:00:00 +0530</pubDate>
    <lastBuildDate>Wed, 06 May 2026 11:52:19 +0530</lastBuildDate>
    <generator>TaxTMI RSS Generator</generator>
    <atom:link href="https://www.taxtmi.com/rss_feed_blog?id=900226" rel="self" type="application/rss+xml"/>
    <item>
      <title>2022 (8) TMI 1622 - DELHI HIGH COURT</title>
      <link>https://www.taxtmi.com/caselaws?id=468438</link>
      <description>Writ jurisdiction under Article 226 depends on the respondent authority being located within the court&#039;s territorial limits or on some part of the cause of action arising there. On the stated facts, the disciplinary proceedings, enquiry, and impugned order all originated in Jharkhand, and the respondent had no office in Delhi. The petitioner&#039;s residence in Delhi was insufficient to confer jurisdiction. The Delhi High Court therefore lacked territorial jurisdiction to entertain the writ petition.</description>
      <category>Case-Laws</category>
      <law>Indian Laws</law>
      <pubDate>Tue, 30 Aug 2022 00:00:00 +0530</pubDate>
      <guid isPermaLink="true">https://www.taxtmi.com/caselaws?id=468438</guid>
    </item>
  </channel>
</rss>